All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hillf Danton <hdanton@sina.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	syzbot <syzbot+222aa26d0a5dbc2e84fe@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] INFO: task hung in synchronize_rcu (4)
Date: Fri, 5 May 2023 18:46:00 +0900	[thread overview]
Message-ID: <c8ce113e-423f-9109-94a1-631583e2ad8e@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20230505083549.GB1770668@hirez.programming.kicks-ass.net>

On 2023/05/05 17:35, Peter Zijlstra wrote:
>> Linus, I think that "[PATCH v3 (repost)] locking/lockdep: add debug_show_all_lock_holders()"
>> helps here, but I can't wake up locking people. What can we do?
> 
> How is that not also racy ?

Nobody can make this code racy.

> 
> I think I've seen that patch, and it had a some 'blurb' Changelog that
> leaves me wondering wtf the actual problem is and how it attempts to
> solve it and I went on with looking at regressions because more
> important than random weird patch.

Please respond to
https://lkml.kernel.org/393a440f-5f82-432c-bc24-e8de33e29d75@I-love.SAKURA.ne.jp .


  reply	other threads:[~2023-05-05  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230504061613.3901-1-hdanton@sina.com>
2023-05-04  7:01 ` [syzbot] [fs?] INFO: task hung in synchronize_rcu (4) Tetsuo Handa
2023-05-05  8:35   ` Peter Zijlstra
2023-05-05  9:46     ` Tetsuo Handa [this message]
2023-05-05  9:49       ` Tetsuo Handa
2023-05-04  2:01 syzbot
2023-05-20 22:13 ` syzbot
2023-05-21  2:26   ` Martin KaFai Lau
2023-05-21  5:04     ` Tetsuo Handa

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=c8ce113e-423f-9109-94a1-631583e2ad8e@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=syzbot+222aa26d0a5dbc2e84fe@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.