From: "Luck, Tony" <tony.luck@intel.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Jens Axboe <axboe@kernel.dk>, Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org
Subject: Re: lockdep warnings from upstream build
Date: Sun, 6 Apr 2025 13:06:11 -0700 [thread overview]
Message-ID: <Z_Les3Izgqkg85_x@agluck-desk3> (raw)
In-Reply-To: <Z_HArDcN1zdd9wdt@agluck-desk3>
On Sat, Apr 05, 2025 at 04:45:50PM -0700, Luck, Tony wrote:
> Several email threads on this over the past few days, but none
> seem to be getting much attention:
>
> https://lore.kernel.org/all/?q=%22%28%26q-%3Eelevator_lock%29%7B%2B.%2B.%7D-%7B4%3A4%7D%2C+at%3A+elv_iosched_store%22
>
> Since tomorrow is "-rc1" day I thought I'd add my lockdep splat to the
> mix.
>
> System is a 2-socket Icelake. Kernel built from:
>
> f4d2ef48250a ("Merge tag 'kbuild-v6.15' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild")
>
> Though I saw the same thing a few days ago, so the problem was
> introduced much earlier in the merge window.
Bisecting leads to this:
ffa1e7ada456 ("block: Make request_queue lockdep splats show up earlier")
Which may be doing what it says on the tin. But, I don't think I've
ever seen the "type 1 splats" on this machine even though every kernel
I build has lockdep enabled.
So it this showing up a real problem that happens to be very difficult
to hit? Or has it introduced a false positive?
-Tony
parent reply other threads:[~2025-04-06 20:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Z_HArDcN1zdd9wdt@agluck-desk3>]
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=Z_Les3Izgqkg85_x@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=thomas.hellstrom@linux.intel.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