mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <song@kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Yu Kuai <yukuai1@huaweicloud.com>,
	"Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: mainline build failure due to 8295efbe68c0 ("md/raid1-10: factor out a helper to submit normal write")
Date: Thu, 29 Jun 2023 14:05:41 -0600	[thread overview]
Message-ID: <d6130a0c-5d91-b0a3-f6a9-d1fa6edbba92@kernel.dk> (raw)
In-Reply-To: <CAPhsuW7VK6O6RKQTAcAVk4XxUzNALUW5nKMnMFkm3pW+4F23yw@mail.gmail.com>

The late branch will go out some time next week.


On 6/29/23 9:56?AM, Song Liu wrote:
> Oops, didn't really add Jens in the previous email.
> 
> Add Jens now.
> 
> On Thu, Jun 29, 2023 at 8:55?AM Song Liu <song@kernel.org> wrote:
>>
>> + Jens,
>>
>> On Thu, Jun 29, 2023 at 7:10?AM Linux regression tracking (Thorsten
>> Leemhuis) <regressions@leemhuis.info> wrote:
>>>
>>> On 29.06.23 15:56, Yu Kuai wrote:
>>>>
>>>> ? 2023/06/29 21:32, Sudip Mukherjee (Codethink) ??:
>>>>> The latest mainline kernel branch fails to build x86_64, arm64 and arm
>>>>> allmodconfig
>>>
>>> Thx for the report.
>>>
>>>> Thanks for the testing, which branch are you testing?
>>>>
>>>> This problem is already fixed in latest mainline kernel:
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b5a99602b74bbfa655be509c615181dd95b0719e
>>
>> Hi Jens,
>>
>> The fix is in the for-6.5/block-late branch.
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-6.5/block-late&id=b5a99602b74bbfa655be509c615181dd95b0719e
>>
>> Would you send a pull request with it? Or would you prefer
>> some other solution for the issue?
>>
>> AFAICT, it will fix clang build with RANDSTRUCT.
>>
>> Thanks,
>> Song
>>
>>>
>>> And thx for the reply. :-D
>>>
>>> FWIW, that fix afaics is still in -next and hasn't reached mainline yet.
>>> But I guess that will change within a few days.
>>>
>>>>> #regzbot introduced: 8295efbe68c080047e98d9c0eb5cb933b238a8cb
>>>
>>> #regzbot fix: b5a99602b74bbfa6
>>> #regzbot dup-of: https://lore.kernel.org/all/ZJ2M4yqnOCqqGWH0@debian/
>>> #regzbot ignore-activity
>>>
>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>> --
>>> Everything you wanna know about Linux kernel regression tracking:
>>> https://linux-regtracking.leemhuis.info/about/#tldr
>>> If I did something stupid, please tell me, as explained on that page.

-- 
Jens Axboe


      reply	other threads:[~2023-06-29 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 13:32 Sudip Mukherjee (Codethink)
2023-06-29 13:56 ` Yu Kuai
2023-06-29 14:06   ` Sudip Mukherjee
2023-06-29 14:09   ` Linux regression tracking (Thorsten Leemhuis)
2023-06-29 15:55     ` Song Liu
2023-06-29 15:56       ` Song Liu
2023-06-29 20:05         ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d6130a0c-5d91-b0a3-f6a9-d1fa6edbba92@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=song@kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yukuai1@huaweicloud.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®