From: syzbot <syzbot+4036165fc595a74b09b2@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, amir73il@gmail.com,
dhowells@redhat.com, edumazet@google.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
sven@narfation.org, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] [overlayfs?] WARNING in file_seek_cur_needs_f_lock
Date: Mon, 07 Apr 2025 14:10:01 -0700 [thread overview]
Message-ID: <67f43f29.050a0220.396535.0554.GAE@google.com> (raw)
In-Reply-To: <67f34d24.050a0220.0a13.027c.GAE@google.com>
syzbot has bisected this issue to:
commit 00b35530811f2aa3d7ceec2dbada80861c7632a8
Author: Eric Dumazet <edumazet@google.com>
Date: Thu Feb 6 14:04:22 2025 +0000
batman-adv: adopt netdev_hold() / netdev_put()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175f8c04580000
start commit: 16cd1c265776 Merge tag 'timers-cleanups-2025-04-06' of git..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14df8c04580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10df8c04580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c79406130aa88d22
dashboard link: https://syzkaller.appspot.com/bug?extid=4036165fc595a74b09b2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f9bd98580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1571c7e4580000
Reported-by: syzbot+4036165fc595a74b09b2@syzkaller.appspotmail.com
Fixes: 00b35530811f ("batman-adv: adopt netdev_hold() / netdev_put()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-04-07 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 3:57 [syzbot] [ext4?] [overlayfs?] WARNING in file_seek_cur_needs_f_lock syzbot
2025-04-07 9:18 ` Miklos Szeredi
2025-04-07 14:07 ` syzbot
2025-04-07 21:02 ` David Howells
2025-04-08 6:17 ` Miklos Szeredi
2025-04-07 21:10 ` syzbot [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=67f43f29.050a0220.396535.0554.GAE@google.com \
--to=syzbot+4036165fc595a74b09b2@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=amir73il@gmail.com \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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