mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
	Song Liu <song@kernel.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	regressions@lists.linux.dev
Subject: Re: mainline build failure due to 8295efbe68c0 ("md/raid1-10: factor out a helper to submit normal write")
Date: Thu, 29 Jun 2023 21:56:11 +0800	[thread overview]
Message-ID: <be9320b5-7613-be0f-ffcd-4b3041ea5836@huaweicloud.com> (raw)
In-Reply-To: <ZJ2H5FWuo9oDMgPm@debian>

Hi,

在 2023/06/29 21:32, Sudip Mukherjee (Codethink) 写道:
> Hi All,
> 
> The latest mainline kernel branch fails to build x86_64, arm64 and arm allmodconfig

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

Kuai
> with clang (version 16.0.1), and the error is:
> 
> In file included from drivers/md/raid1.c:52:
> drivers/md/raid1-10.c:119:25: error: casting from randomized structure pointer type 'struct block_device *' to 'struct md_rdev *'
>          struct md_rdev *rdev = (struct md_rdev *)bio->bi_bdev;
>                                 ^
> 
> git bisect pointed to 8295efbe68c0 ("md/raid1-10: factor out a helper to submit normal write").
> 
> Reverting the commit has fixed the build failure.
> 
> I will be happy to test any patch or provide any extra log if needed.
> 
> #regzbot introduced: 8295efbe68c080047e98d9c0eb5cb933b238a8cb
> 


  reply	other threads:[~2023-06-29 13:56 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 [this message]
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

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=be9320b5-7613-be0f-ffcd-4b3041ea5836@huaweicloud.com \
    --to=yukuai1@huaweicloud.com \
    --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 \
    /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®