linux-kernel - Re: linux-next: Fixes tag needs some work in the block 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: <c39a3bff-01b9-4007-80ac-00ce2b11a902@kernel.dk>
Date:   Tue, 15 Aug 2023 09:08:02 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Yu Kuai <yukuai1@...weicloud.com>,
        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>,
        "yukuai (C)" <yukuai3@...wei.com>,
        "song@...nel.org" <song@...nel.org>
Subject: Re: linux-next: Fixes tag needs some work in the block tree

On 8/14/23 9:21 PM, Yu Kuai wrote:
> Hi,
> 
> ? 2023/08/15 7:19, Stephen Rothwell ??:
>> Hi all,
>>
>> In commit
>>
>>    71070e7bd25d ("md/raid10: fix a 'conf->barrier' leakage in raid10_takeover()")
>>
>> Fixes tag
>>
>>    Fixes: 4d27e927344a ("md: don't quiesce in mddev_suspend()")
>>
>> has these problem(s):
>>
>>    - Target SHA1 does not exist
> 
> Sorry about this, the commit was picked from previous md-next branch,
> and I didn't know that it will change...

It's most likely not your fault, I'm guessing Song rebased that branch
and this is why the sha changed. Song?

> Is there any way that I can fix this ?

Only way to fix this is if I rewind my branch and Song updates his
branch to not have this issue, and then sends a new pull request.

-- 
Jens Axboe