lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 30 Oct 2017 15:14:33 -0700 (PDT)
From:   Stefano Stabellini <sstabellini@...nel.org>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>
cc:     Stefano Stabellini <sstabellini@...nel.org>,
        xen-devel@...ts.xen.org, linux-kernel@...r.kernel.org,
        jgross@...e.com, Stefano Stabellini <stefano@...reto.com>
Subject: Re: [PATCH v7 13/13] xen: introduce a Kconfig option to enable the
 pvcalls frontend

On Mon, 30 Oct 2017, Boris Ostrovsky wrote:
> On 10/30/2017 05:42 PM, Stefano Stabellini wrote:
> > On Mon, 30 Oct 2017, Boris Ostrovsky wrote:
> >> On 10/30/2017 03:48 PM, Stefano Stabellini wrote:
> >>> On Mon, 30 Oct 2017, Boris Ostrovsky wrote:
> >>>> Build warnings (gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1))
> >>> Hi Boris, I am trying to repro the warnings below. I have been
> >>> unsuccessful so far. What system are you using? Fedora? CentOS? Do have
> >>> any specific CFLAGS settings?
> >>
> >> I am on Fedora24, nothing interesting in my environment. For example,
> >>
> >> ostr@...kbase> env | grep FLAGS
> >> ostr@...kbase>
> >>
> >> I'll send you my config file in a separate email, just in case.  Your
> >> patches are on top of
> >>
> >>     0b07194 Linux 4.14-rc7
> >>
> > Thanks! I managed to repro and fix both the x86_64 and x86_32 issues.
> > I sent two patches:
> >
> > https://marc.info/?l=xen-devel&m=150939969002183&w=2
> > https://marc.info/?l=linux-kernel&m=150939962102165
> >
> > But if you prefer that I spin a new pvcalls frontend series, I could
> > also do that.
> 
> 
> I haven't pushed this anywhere so I think, given that this actually
> fixes a bug (when copy_to/from_iter() fails), it would be better to have
> a clean series in the upstream. So I'd rather have a new spin, sorry ;-(

No problem! I'll send one out shortly.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ