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]
Message-ID: <20170420195624.GJ128305@google.com>
Date:   Thu, 20 Apr 2017 12:56:24 -0700
From:   Matthias Kaehlcke <mka@...omium.org>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Alexander Viro <viro@...iv.linux.org.uk>,
        Mark Charlebois <charlebm@...il.com>,
        Behan Webster <behanw@...verseincode.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
        Grant Grundler <grundler@...omium.org>,
        Michael Davidson <md@...gle.com>,
        Greg Hackmann <ghackmann@...gle.com>,
        Peter Foley <pefoley2@...oley.com>
Subject: Re: [PATCH] fs: compat: Remove warning from COMPATIBLE_IOCTL

El Thu, Apr 20, 2017 at 10:45:47AM +0200 Arnd Bergmann ha dit:

> On Wed, Apr 19, 2017 at 11:37 PM, Matthias Kaehlcke <mka@...omium.org> wrote:
> > El Wed, Apr 19, 2017 at 10:48:47PM +0200 Arnd Bergmann ha dit:
> >> On Wed, Apr 19, 2017 at 8:14 PM, Matthias Kaehlcke <mka@...omium.org> wrote:
> >> > El Tue, Apr 04, 2017 at 11:07:20AM -0700 Matthias Kaehlcke ha dit:
> 
> >> Aside from that, I see that you are upstreaming a number of clang
> >> related patches. I actually have a longer series of clang patches that
> >> I took from llvmlinux and hacked up to the point where I could
> >> build ARM randconfig kernels without any warnings or errors.
> >> If you are interested, I can separate the clang patches from my normal
> >> randconfig build tree and upload the git tree for you to look at and
> >> cherry-pick further patches.
> >
> > Sure, that would be interesting, though I won't promise to take up
> > everything :)
> 
> I see now that almost all the patches I did have been picked up in the
> meantime, so I'm sure you already have most of the remaining contents
> as they come from the old llvmlinux project.

Yeah, I picked a subset of the llvmlinux patches from different
sources.

> For reference, I've uploaded my set to
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
> next-20170420+llvmlinux
> 
> This is rebased from the middle of a larger series, so there might be
> problems I introduce. Just have a look to see what you can use.

Thanks!

Matthias

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ