From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
syzbot <syzbot+972b924c988834e868b2@syzkaller.appspotmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Josh Triplett <josh@joshtriplett.org>,
rcu@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Peter Rosin <peda@axentia.se>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: WARNING: suspicious RCU usage in modeset_lock
Date: Sat, 19 Dec 2020 10:00:02 +0900 [thread overview]
Message-ID: <c0ed329a-1349-5d07-5b60-0a89d9fb9de3@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CACT4Y+bABW7OP0RDm-Qnq2M6kKVTc=e7Tmt5Uc1+zWyD2roqrA@mail.gmail.com>
On Wed, Dec 16, 2020 at 5:16 PM Paul E. McKenney <paulmck@kernel.org> wrote:
> In my experience, lockdep will indeed complain if an interrupt handler
> returns while in an RCU read-side critical section.
Can't we add lock status checks into the beginning and the end of interrupt handler functions
(e.g. whether "struct task_struct"->lockdep_depth did not change) ?
next prev parent reply other threads:[~2020-12-19 1:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 1:14 WARNING: suspicious RCU usage in modeset_lock syzbot
2020-12-16 9:52 ` Daniel Vetter
2020-12-16 16:16 ` Paul E. McKenney
2020-12-17 8:28 ` Dmitry Vyukov
2020-12-17 10:03 ` Daniel Vetter
2020-12-17 15:21 ` Paul E. McKenney
2020-12-18 1:29 ` Boqun Feng
2020-12-18 11:27 ` Dmitry Vyukov
2020-12-19 1:00 ` Tetsuo Handa [this message]
2020-12-21 15:55 ` Boqun Feng
2020-12-18 16:10 ` Steven Rostedt
2020-12-18 16:23 ` Daniel Vetter
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=c0ed329a-1349-5d07-5b60-0a89d9fb9de3@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=b.zolnierkie@samsung.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=gustavoars@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=paulmck@kernel.org \
--cc=peda@axentia.se \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=syzbot+972b924c988834e868b2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).