From: syzbot <syzbot+96eb4e0d727f0ae998a6@syzkaller.appspotmail.com>
To: broonie@kernel.org, dave.kleikamp@oracle.com,
davem@davemloft.net, edumazet@google.com, jason@zx2c4.com,
jfs-discussion@lists.sourceforge.net, kuba@kernel.org,
kuninori.morimoto.gx@renesas.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, lists@nerdbynature.de,
netdev@vger.kernel.org, pabeni@redhat.com, povik@cutebit.org,
syzkaller-bugs@googlegroups.com, wireguard@lists.zx2c4.com
Subject: Re: [syzbot] [wireguard?] [jfs?] KASAN: slab-use-after-free Read in wg_noise_keypair_get
Date: Wed, 19 Jul 2023 10:52:36 -0700 [thread overview]
Message-ID: <00000000000069291b0600dab2d6@google.com> (raw)
In-Reply-To: <30f03978-3035-a28e-c097-112036901bcb@nerdbynature.de>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+96eb4e0d727f0ae998a6@syzkaller.appspotmail.com
Tested on:
commit: 6e2bda2c jfs: fix invalid free of JFS_IP(ipimap)->i_im..
git tree: https://github.com/kleikamp/linux-shaggy.git
console output: https://syzkaller.appspot.com/x/log.txt?x=172aecaaa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f631232ee56196bd
dashboard link: https://syzkaller.appspot.com/bug?extid=96eb4e0d727f0ae998a6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2023-07-19 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 15:21 syzbot
2023-07-18 17:57 ` Jason A. Donenfeld
2023-07-18 21:02 ` Dave Kleikamp
2023-07-19 15:02 ` [Jfs-discussion] " Christian Kujau
2023-07-19 17:52 ` 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=00000000000069291b0600dab2d6@google.com \
--to=syzbot+96eb4e0d727f0ae998a6@syzkaller.appspotmail.com \
--cc=broonie@kernel.org \
--cc=dave.kleikamp@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jason@zx2c4.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=kuba@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=povik@cutebit.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).