netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+9a0875bc1b2ca466b484@syzkaller.appspotmail.com>
To: davem@davemloft.net, jiri@nvidia.com, johan.hedberg@gmail.com,
	kuba@kernel.org, leonro@nvidia.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	luiz.dentz@gmail.com, marcel@holtmann.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	wanjiabing@vivo.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in lock_sock_nested
Date: Wed, 24 Nov 2021 13:19:13 -0800	[thread overview]
Message-ID: <000000000000d9412505d18f6899@google.com> (raw)
In-Reply-To: <000000000000e2852705ac9cfd73@google.com>

syzbot suspects this issue was fixed by commit:

commit c5e0321e43deed0512b34d8d8d40a16c0e22b541
Author: Leon Romanovsky <leonro@nvidia.com>
Date:   Tue Oct 26 19:40:42 2021 +0000

    Revert "devlink: Remove not-executed trap policer notifications"

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10f87adeb00000
start commit:   a409ed156a90 Merge tag 'gpio-v5.11-1' of git://git.kernel...
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=20efebc728efc8ff
dashboard link: https://syzkaller.appspot.com/bug?extid=9a0875bc1b2ca466b484
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10a4445b500000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Revert "devlink: Remove not-executed trap policer notifications"

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2021-11-24 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 16:59 KASAN: slab-out-of-bounds Read in lock_sock_nested syzbot
2020-12-19  7:56 ` syzbot
2021-11-24 21:19 ` 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=000000000000d9412505d18f6899@google.com \
    --to=syzbot+9a0875bc1b2ca466b484@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wanjiabing@vivo.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).