From: Paolo Abeni <pabeni@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
syzbot+6cffdef928852907751c@syzkaller.appspotmail.com,
"David S. Miller" <davem@davemloft.net>
Cc: Borislav Petkov <bp@suse.de>, Jason Baron <jbaron@akamai.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
syzkaller-bugs@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: WARNING in static_key_disable_cpuslocked
Date: Sat, 17 Nov 2018 17:25:43 +0100 [thread overview]
Message-ID: <93ee204b846462f9ead610e5afe737389724d0aa.camel@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8tJZUgL7q0R2KvGdyK+_y1U7KHQNDMpCmM7ZGprkKajg@mail.gmail.com>
Hi,
On Sat, 2018-11-17 at 06:52 -0800, Ard Biesheuvel wrote:
> (+ Paolo, Dave)
>
> On Sat, 17 Nov 2018 at 01:59, syzbot
> <syzbot+6cffdef928852907751c@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: 442b8cea2477 Add linux-next specific files for 20181109
> > git tree: linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=11f1dc25400000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=2f72bdb11df9fbe8
> > dashboard link: https://syzkaller.appspot.com/bug?extid=6cffdef928852907751c
> > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10126533400000
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+6cffdef928852907751c@syzkaller.appspotmail.com
This should be addressed in current net-next, by commit:
commit 9c48060141bd937497774546e4bb89b8992be383
Author: Paolo Abeni <pabeni@redhat.com>
Date: Thu Nov 15 02:34:50 2018 +0100
udp: fix jump label misuse
Cheers,
Paolo
next prev parent reply other threads:[~2018-11-17 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 9:59 WARNING in static_key_disable_cpuslocked syzbot
2018-11-17 14:52 ` Ard Biesheuvel
2018-11-17 16:25 ` Paolo Abeni [this message]
2018-11-17 17:08 ` Dmitry Vyukov
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=93ee204b846462f9ead610e5afe737389724d0aa.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=davem@davemloft.net \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+6cffdef928852907751c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).