All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e6741b97d5552f97c24d@syzkaller.appspotmail.com>
To: davem@davemloft.net, devicetree@vger.kernel.org,
	frowand.list@gmail.com, gregkh@linuxfoundation.org,
	jmaloy@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, paskripkin@gmail.com, rafael@kernel.org,
	robh@kernel.org, syzkaller-bugs@googlegroups.com,
	tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com
Subject: Re: [syzbot] KASAN: use-after-free Read in tipc_recvmsg
Date: Fri, 23 Jul 2021 16:10:09 -0700	[thread overview]
Message-ID: <00000000000042305105c7d281d0@google.com> (raw)
In-Reply-To: <20210723194932.6c3b77a8@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+e6741b97d5552f97c24d@syzkaller.appspotmail.com

Tested on:

commit:         90d856e7 Add linux-next specific files for 20210723
git tree:       linux-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=644211b3d3da598c
dashboard link: https://syzkaller.appspot.com/bug?extid=e6741b97d5552f97c24d
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
patch:          https://syzkaller.appspot.com/x/patch.diff?x=118f857c300000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2021-07-23 23:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 17:15 [syzbot] KASAN: use-after-free Read in tipc_recvmsg syzbot
2021-07-23 16:36 ` Pavel Skripkin
2021-07-23 16:41   ` Xin Long
2021-07-23 16:52     ` Pavel Skripkin
2021-07-23 16:49   ` Pavel Skripkin
2021-07-23 23:10     ` syzbot [this message]
2021-07-23 22:51   ` 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=00000000000042305105c7d281d0@google.com \
    --to=syzbot+e6741b97d5552f97c24d@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paskripkin@gmail.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.