From: syzbot <syzbot+382c8824777dca2812fe@syzkaller.appspotmail.com>
To: chuck.lever@oracle.com, frederic@kernel.org, hdanton@sina.com,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, rafael.j.wysocki@intel.com,
syzkaller-bugs@googlegroups.com, tony@atomide.com,
ulf.hansson@linaro.org, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] KASAN: use-after-free Read in kill_fasync
Date: Fri, 03 Mar 2023 16:24:27 -0800 [thread overview]
Message-ID: <000000000000ac777e05f6081529@google.com> (raw)
In-Reply-To: <0000000000001544f005e381d722@google.com>
syzbot suspects this issue was fixed by commit:
commit 69d4c0d3218692ffa56b0e1b9c76c50c699d7044
Author: Peter Zijlstra <peterz@infradead.org>
Date: Thu Jan 12 19:43:58 2023 +0000
entry, kasan, x86: Disallow overriding mem*() functions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17adfae4c80000
start commit: 972a278fe60c Merge tag 'for-5.19-rc7-tag' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3cc990589d31f8d6
dashboard link: https://syzkaller.appspot.com/bug?extid=382c8824777dca2812fe
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141c2dac080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1590cfa4080000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: entry, kasan, x86: Disallow overriding mem*() functions
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-03-04 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 6:41 [syzbot] KASAN: use-after-free Read in kill_fasync syzbot
2023-03-04 0:24 ` 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=000000000000ac777e05f6081529@google.com \
--to=syzbot+382c8824777dca2812fe@syzkaller.appspotmail.com \
--cc=chuck.lever@oracle.com \
--cc=frederic@kernel.org \
--cc=hdanton@sina.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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