linux-kernel - Re: linux-next: Fixes tag needs some work in the btrfs-fixes tree

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: <20201027141122.GD6756@suse.cz>
Date:   Tue, 27 Oct 2020 15:11:22 +0100
From:   David Sterba <dsterba@...e.cz>
To:     Johannes Thumshirn <Johannes.Thumshirn@....com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the btrfs-fixes tree

On Mon, Oct 26, 2020 at 03:04:40PM +0000, Johannes Thumshirn wrote:
> On 26/10/2020 16:01, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >   ae1a53ee21a5 ("btrfs: don't fallback to buffered read if we don't need to")
> > 
> > Fixes tag
> > 
> >   Fixes: b5ff9f1a96e8f ("btrfs: switch to iomap for direct IO")
> > 
> > has these problem(s):
> > 
> >   - Target SHA1 does not exist
> > 
> > Maybe you meant
> > 
> > Fixes: f85781fb505e ("btrfs: switch to iomap for direct IO")
> > 
> 
> Hmm b5ff9f1a96e8f exists in my tree. Probably something stale.

Same for me, the correct one is indeed f85781fb505ec028917, I'll push
an update.