linux-kernel - Re: linux-next: duplicate patch in the mm-nonmm-stable 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230220151211.1cdec7528db28a00320a855f@linux-foundation.org>
Date:   Mon, 20 Feb 2023 15:12:11 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Jan Kara <jack@...e.cz>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the mm-nonmm-stable tree

On Tue, 21 Feb 2023 09:08:27 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>   bf470202dd9f ("fs: gracefully handle ->get_block not mapping bh in __mpage_writepage")

CommitDate: Thu Feb 2 22:50:07 2023 -0800

> This is commit
> 
>   7010839ccfd4 ("fs: gracefully handle ->get_block not mapping bh in __mpage_writepage")
> 
> in Linus' tree.

CommitDate: Thu Jan 26 16:46:35 2023 +0100


So I'm wondering why this came to light on Feb 20?

Thanks.