linux-kernel - Re: linux-next: bad commits in the v9fs 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: <Yqe2CT0whmf8mYLj@codewreck.org>
Date:   Tue, 14 Jun 2022 07:11:21 +0900
From:   Dominique Martinet <asmadeus@...ewreck.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: bad commits in the v9fs tree

Stephen Rothwell wrote on Tue, Jun 14, 2022 at 07:52:23AM +1000:
>   04608d78b66c ("Linux 5.19-rc1")
>   9383b9134c66 ("fix the breakage in close_fd_get_file() calling conventions change")
> 
> look like they were rebased or cherry-picked from Linus' tree.from
> Linus' tree.  From commits f2906aa86338 and 40a1926022d1 respectively.

Ugh, thank you for noticing.
I had an overly eager `rebase -i` that are usually noop and don't touch
the top patches if left alone, but that only works if no merge is
involved and that wasn't the case here -- I'll be more careful with my
rebase root from now on so it hopefully won't happen again.

Fixed my 9p-next branch so these two should be gone next time you
update.

Thanks,
-- 
Dominique