From: Jan Kara <jack@suse.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: syzbot <syzbot+f816042a7ae2225f25ba@syzkaller.appspotmail.com>,
adi@adirat.com, alsa-devel@alsa-project.org,
coreteam@netfilter.org, davem@davemloft.net, jack@suse.com,
kaber@trash.net, kadlec@blackhole.kfki.hu,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
perex@perex.cz, syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: Re: BUG: unable to handle kernel paging request in dqput
Date: Tue, 29 Sep 2020 16:30:31 +0200 [thread overview]
Message-ID: <20200929143031.GP10896@quack2.suse.cz> (raw)
In-Reply-To: <s5htuvjpujt.wl-tiwai@suse.de>
On Sun 27-09-20 09:07:02, Takashi Iwai wrote:
> On Sat, 26 Sep 2020 22:48:15 +0200,
> syzbot wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17930875900000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=af502ec9a451c9fc
> > dashboard link: https://syzkaller.appspot.com/bug?extid=f816042a7ae2225f25ba
> > compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=133783ab900000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13bb5973900000
> >
> > The issue was bisected to:
> >
> > commit 1d0f953086f090a022f2c0e1448300c15372db46
> > Author: Ioan-Adrian Ratiu <adi@adirat.com>
> > Date: Wed Jan 4 22:37:46 2017 +0000
> >
> > ALSA: usb-audio: Fix irq/process data synchronization
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=133362c3900000
> > final oops: https://syzkaller.appspot.com/x/report.txt?x=10b362c3900000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=173362c3900000
>
> This commit looks really irrelevant from the Oops code path.
> It must be a different reason.
Yeah, it seems the bisection got confused because it hit a different error
during the bisection. Looking at the original oops, I think the actual
reason of a crash is that quota file got corrupted in a particular way.
Quota code is not very paranoid when checking on disk contents. I'll work
on adding more sanity checks to quota code...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-09-29 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 20:48 BUG: unable to handle kernel paging request in dqput syzbot
2020-09-27 7:07 ` Takashi Iwai
2020-09-29 14:30 ` Jan Kara [this message]
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=20200929143031.GP10896@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adi@adirat.com \
--cc=alsa-devel@alsa-project.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=jack@suse.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=perex@perex.cz \
--cc=syzbot+f816042a7ae2225f25ba@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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).