From: "Lai, Yi" <yi1.lai@linux.intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [Syzkaller & bisect] There is INFO: task hung in __rq_qos_throttle
Date: Fri, 25 Oct 2024 17:52:57 +0800 [thread overview]
Message-ID: <ZxtqeYRHz3hQrR0f@ly-workstation> (raw)
In-Reply-To: <kuvbuekbzs6saggfxleiaqtl5mleozqozpamivz2zo6pd4istq@c6hfl6govn44>
On Wed, Oct 23, 2024 at 09:57:53PM -0400, Kent Overstreet wrote:
> On Mon, Oct 21, 2024 at 06:27:25PM +0800, Lai, Yi wrote:
> > Hi Kent Overstreet,
> >
> > Greetings!
> >
> > I used Syzkaller and found that there is INFO: task hung in __rq_qos_throttle in v6.12-rc2
> >
> > After bisection and the first bad commit is:
> > "
> > 63332394c7e1 bcachefs: Move snapshot table size to struct snapshot_table
>
> You sure...?
>
> Look at the patch, that's a pretty unlikely culprit; we would've seen
> something from kasan, and anyways there's guards on the new memory
> accesses/array derefs.
>
> I've been seeing that bug too, but it's very intermittent. How did you
> get it to trigger reliably enough for a bisect?
Look into my local bisection log. You are right, that the bug is intermittent
and takes a very long time to reproduce the issue.
I didn't observe similar issues during following v6.12-rcx kernel
fuzzing. I will keep monitoring.
Regards,
Yi Lai
next prev parent reply other threads:[~2024-10-25 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 10:27 [Syzkaller & bisect] There is INFO: task hung in __rq_qos_throttle Lai, Yi
2024-10-24 1:57 ` Kent Overstreet
2024-10-25 9:52 ` Lai, Yi [this message]
2024-10-25 10:02 ` Kent Overstreet
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=ZxtqeYRHz3hQrR0f@ly-workstation \
--to=yi1.lai@linux.intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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