All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+10a7a8ca6e94600110ec@syzkaller.appspotmail.com>
To: axboe@kernel.dk, gakula@marvell.com, hdanton@sina.com,
	jiasheng@iscas.ac.cn, justin@coraid.com, kuba@kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	michal.swiatkowski@linux.intel.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] KASAN: use-after-free Read in netdev_core_pick_tx
Date: Fri, 31 Mar 2023 08:42:22 -0700	[thread overview]
Message-ID: <00000000000020d46805f8340e6b@google.com> (raw)
In-Reply-To: <000000000000a5c9be05ed85b31b@google.com>

syzbot suspects this issue was fixed by commit:

commit f038f3917baf04835ba2b7bcf2a04ac93fbf8a9c
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Mar 17 06:43:37 2023 +0000

    octeontx2-vf: Add missing free for alloc_percpu

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=133a3d2ec80000
start commit:   42226c989789 Linux 5.18-rc7
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=d84df8e1a4c4d5a4
dashboard link: https://syzkaller.appspot.com/bug?extid=10a7a8ca6e94600110ec
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11ed1369f00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=166b22cef00000

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

#syz fix: octeontx2-vf: Add missing free for alloc_percpu

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

  reply	other threads:[~2023-03-31 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 17:29 [syzbot] KASAN: use-after-free Read in netdev_core_pick_tx syzbot
2023-03-31 15:42 ` syzbot [this message]
2023-03-31 15:48   ` [syzbot] [block?] " Aleksandr Nogikh

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=00000000000020d46805f8340e6b@google.com \
    --to=syzbot+10a7a8ca6e94600110ec@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=gakula@marvell.com \
    --cc=hdanton@sina.com \
    --cc=jiasheng@iscas.ac.cn \
    --cc=justin@coraid.com \
    --cc=kuba@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=syzkaller-bugs@googlegroups.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.