From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+d472c32c5dd4cd2fb5c5@syzkaller.appspotmail.com>
Cc: daniel.vetter@ffwll.ch, jack@suse.com,
linux-kernel@vger.kernel.org, mairacanal@riseup.net,
mcanal@igalia.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] possible deadlock in udf_free_blocks
Date: Tue, 3 Dec 2024 14:01:00 +0100 [thread overview]
Message-ID: <20241203130100.vgqav3cs7pvvyk5s@quack3> (raw)
In-Reply-To: <674efc5f.050a0220.48a03.0035.GAE@google.com>
On Tue 03-12-24 04:41:03, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 7908632f2927b65f7486ae6b67c24071666ba43f
> Author: Maíra Canal <mcanal@igalia.com>
> Date: Thu Sep 14 10:19:02 2023 +0000
>
> Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"
This is obviously bogus. Apparently the reproducer is not quite reliable...
But I can see where's the problem in UDF code.
Honza
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13dbe80f980000
> start commit: cdd30ebb1b9f module: Convert symbol namespace to string li..
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=103be80f980000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17dbe80f980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=91c852e3d1d7c1a6
> dashboard link: https://syzkaller.appspot.com/bug?extid=d472c32c5dd4cd2fb5c5
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=117440f8580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1659b5e8580000
>
> Reported-by: syzbot+d472c32c5dd4cd2fb5c5@syzkaller.appspotmail.com
> Fixes: 7908632f2927 ("Revert "drm/vkms: Fix race-condition between the hrtimer and the atomic commit"")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-12-03 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:57 syzbot
2024-12-03 3:56 ` syzbot
2024-12-03 12:41 ` syzbot
2024-12-03 13:01 ` Jan Kara [this message]
2024-12-11 4:53 ` syzbot
2025-04-15 15:12 ` Jeongjun Park
2025-04-15 15:36 ` syzbot
2025-04-15 15:42 ` Jeongjun Park
2025-04-15 18:33 ` syzbot
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=20241203130100.vgqav3cs7pvvyk5s@quack3 \
--to=jack@suse.cz \
--cc=daniel.vetter@ffwll.ch \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=mcanal@igalia.com \
--cc=syzbot+d472c32c5dd4cd2fb5c5@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
all inboxes | Powered by JetHome®