From: Peter Zijlstra <peterz@infradead.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: mingo@redhat.com, will@kernel.org, boqun@kernel.org,
longman@redhat.com, linux-kernel@vger.kernel.org,
syzbot+0635dc2e2c3c21a6aa04@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] locking/lockdep: skip irq save/restore in hardirq context in lock_release()
Date: Tue, 30 Jun 2026 11:50:41 +0200 [thread overview]
Message-ID: <20260630095041.GB751831@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260629233650.90279-1-kartikey406@gmail.com>
On Tue, Jun 30, 2026 at 05:06:50AM +0530, Deepanshu Kartikey wrote:
> lock_release() performs a raw_local_irq_save/restore dance around its
> validation work. While safe in process and softirq context, this is
> dangerous in hardirq context where IRQs must remain disabled for the
> entire duration of the handler.
>
> When lock_release() calls raw_local_irq_restore() inside a hardirq
> handler, it briefly re-enables IRQs,
It does not.
next prev parent reply other threads:[~2026-06-30 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 23:36 Deepanshu Kartikey
2026-06-30 9:50 ` Peter Zijlstra [this message]
2026-07-03 1:06 ` Deepanshu Kartikey
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=20260630095041.GB751831@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=syzbot+0635dc2e2c3c21a6aa04@syzkaller.appspotmail.com \
--cc=will@kernel.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®