From: syzbot <syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
bjorn.topel@intel.com, bp@alien8.de, bpf@vger.kernel.org,
daniel@iogearbox.net, dave.hansen@linux.intel.com,
davem@davemloft.net, hawk@kernel.org, hpa@zytor.com,
john.fastabend@gmail.com, jonathan.lemon@gmail.com, kafai@fb.com,
kpsingh@chromium.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luto@kernel.org, magnus.karlsson@intel.com,
marekx.majtyka@intel.com, mingo@kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, peterz@infradead.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org, yhs@fb.com
Subject: Re: kernel BUG at mm/vmalloc.c:LINE! (2)
Date: Sun, 10 Jan 2021 13:34:05 -0800 [thread overview]
Message-ID: <00000000000087569605b8928ce3@google.com> (raw)
In-Reply-To: <000000000000588c2c05aa156b2b@google.com>
syzbot suspects this issue was fixed by commit:
commit 537cf4e3cc2f6cc9088dcd6162de573f603adc29
Author: Magnus Karlsson <magnus.karlsson@intel.com>
Date: Fri Nov 20 11:53:39 2020 +0000
xsk: Fix umem cleanup bug at socket destruct
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=139f3dfb500000
start commit: e87d24fc Merge branch 'net-iucv-fixes-2020-11-09'
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=61033507391c77ff
dashboard link: https://syzkaller.appspot.com/bug?extid=5f326d255ca648131f87
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d10006500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126c9eaa500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: xsk: Fix umem cleanup bug at socket destruct
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-01-10 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:24 kernel BUG at mm/vmalloc.c:LINE! (2) syzbot
2020-07-20 16:48 ` syzbot
2020-07-20 16:48 ` syzbot
2020-07-20 20:06 ` Uladzislau Rezki
2020-07-22 14:28 ` Qian Cai
2020-07-22 14:46 ` Uladzislau Rezki
2020-07-24 2:50 ` Andrew Morton
2020-07-24 3:11 ` Stephen Rothwell
2020-07-24 4:28 ` Stephen Rothwell
2020-07-24 7:47 ` Thomas Gleixner
2020-07-22 6:17 ` syzbot
2020-07-22 6:17 ` syzbot
2021-01-10 21:34 ` syzbot [this message]
2021-01-10 21:34 ` syzbot
2021-01-11 9:15 ` Dmitry Vyukov
2022-01-24 17:59 ` Vegard Nossum
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=00000000000087569605b8928ce3@google.com \
--to=syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=marekx.majtyka@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhs@fb.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.