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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170707140002.GA9755@lst.de>
Date:   Fri, 7 Jul 2017 16:00:02 +0200
From:   Christoph Hellwig <hch@....de>
To:     Al Viro <viro@...IV.linux.org.uk>
Cc:     Christoph Hellwig <hch@....de>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Christopher Li <sparse@...isli.org>
Subject: Re: [git pull] vfs.git part 3

On Fri, Jul 07, 2017 at 12:27:49AM +0100, Al Viro wrote:
> On Thu, Jul 06, 2017 at 11:44:49PM +0200, Christoph Hellwig wrote:
> > > Which sparse version are you using and what's your .config?
> > 
> > sparse is v0.5.0-62-gce18a90, .config is attached.
> 
> Arrgh...  OK, I see what's going on.  sparse commit affecting that
> is "Allow casting to a restricted type if !restricted_value"; it
> allows the things like (__le32)0.  It's present in sparse.git,
> but not in chrisl/sparse.git, which is what you are using.

So what's the current story on sparse versions to use and releases?

At some point it seemed like upstream sparse was sort of dead
and the chrisl repo was the one to use.  It seems the main sparse
repo on git.kernel.org is now identical to the chrisl one, and he
is doing the releases.  So maybe I'll just need to upgrade..

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ