netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	andrii@kernel.org, "Alexei Starovoitov" <ast@kernel.org>,
	"Björn Töpel" <bjorn.topel@intel.com>,
	"Borislav Petkov" <bp@alien8.de>, bpf <bpf@vger.kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"David Miller" <davem@davemloft.net>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"John Fastabend" <john.fastabend@gmail.com>,
	jonathan.lemon@gmail.com, "Martin KaFai Lau" <kafai@fb.com>,
	"KP Singh" <kpsingh@chromium.org>,
	"Jakub Kicinski" <kuba@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Karlsson, Magnus" <magnus.karlsson@intel.com>,
	marekx.majtyka@intel.com, "Ingo Molnar" <mingo@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>, netdev <netdev@vger.kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Song Liu" <songliubraving@fb.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"Yonghong Song" <yhs@fb.com>
Subject: Re: kernel BUG at mm/vmalloc.c:LINE! (2)
Date: Mon, 11 Jan 2021 10:15:58 +0100	[thread overview]
Message-ID: <CACT4Y+a3Xe11dAkRAAewXQ7b=KzK1pk36Arwq=vCR7R-KQy9DQ@mail.gmail.com> (raw)
In-Reply-To: <00000000000087569605b8928ce3@google.com>

On Sun, Jan 10, 2021 at 10:34 PM syzbot
<syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com> wrote:
>
> 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

FTR, the bisection log looks clean, but this does not look like the
fix for this. The reproducer does not destroy sockets.

  reply	other threads:[~2021-01-11  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000588c2c05aa156b2b@google.com>
2021-01-10 21:34 ` kernel BUG at mm/vmalloc.c:LINE! (2) syzbot
2021-01-11  9:15   ` Dmitry Vyukov [this message]
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='CACT4Y+a3Xe11dAkRAAewXQ7b=KzK1pk36Arwq=vCR7R-KQy9DQ@mail.gmail.com' \
    --to=dvyukov@google.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=syzbot+5f326d255ca648131f87@syzkaller.appspotmail.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 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).