From: syzbot <[email protected]>
To: [email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] KASAN: use-after-free Read in filp_close
Date: Sun, 05 Jun 2022 07:04:10 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
syzbot has bisected this issue to:
commit 6319194ec57b0452dcda4589d24c4e7db299c5bf
Author: Al Viro <[email protected]>
Date: Thu May 12 21:08:03 2022 +0000
Unify the primitives for file descriptor closing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=134cbe4ff00000
start commit: 952923ddc011 Merge tag 'pull-18-rc1-work.namei' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10ccbe4ff00000
console output: https://syzkaller.appspot.com/x/log.txt?x=174cbe4ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3096247591885bfa
dashboard link: https://syzkaller.appspot.com/bug?extid=47dd250f527cb7bebf24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114f7bcdf00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1659a94ff00000
Reported-by: [email protected]
Fixes: 6319194ec57b ("Unify the primitives for file descriptor closing")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2022-06-05 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2022-06-05 14:04 ` syzbot [this message]
2022-06-05 16:15 ` [syzbot] KASAN: use-after-free Read in filp_close Al Viro
2022-06-05 18:10 ` Al Viro
2022-06-05 18:29 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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