linux-kernel - Re: Linux 5.6-rc2

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 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]

Date:   Mon, 17 Feb 2020 11:45:32 -0500
From:   Dave Jones <davej@...emonkey.org.uk>
To:     dsterba@...e.cz, Linus Torvalds <torvalds@...ux-foundation.org>,
        Josef Bacik <josef@...icpanda.com>,
        Filipe Manana <fdmanana@...e.com>,
        David Sterba <dsterba@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.6-rc2

On Mon, Feb 17, 2020 at 01:30:54PM +0100, David Sterba wrote:
 > On Sun, Feb 16, 2020 at 09:08:18PM -0800, Linus Torvalds wrote:
 > > On Sun, Feb 16, 2020 at 7:02 PM Josef Bacik <josef@...icpanda.com> wrote:
 > > >
 > > > I assume Filipe wrote this based on my patch here
 > > >
 > > > https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git/commit/?id=c821555d2b9733d8f483c9e79481c7209e1c1fb0
 > > >
 > > > which makes it so we can allocate safely in this context, but that patch hasn't
 > > > made it's way to you yet.  Do you want it now?  It was prep for a much less safe
 > > > patchset, but is fine by itself.  Thanks,
 > > 
 > > I assume it's either that, or revert 28553fa992cb and do it differently..
 > > 
 > > I'll leave that whole decision to the btrfs people who actually know
 > > the code and the situations and what the alternative would look
 > > like...
 > 
 > I'll send a pull request with fix today. The fixes get cherry-picked
 > from development branch to current rc branch and sometimes affect each
 > other. I do test the rc branch independently before sending but I
 > haven't seen the bug Dave reported.

After rebooting, it didn't reproduce, so it did seem to be dependent on
exactly which files rsync was moving around.  Given it doesn't happen
all the time, little surprise it slipped through I guess.

	Dave