From: Sasha Levin <sashal@kernel.org>
To: Zubin Mithra <zsm@chromium.org>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
groeck@chromium.org, davej@codemonkey.org.uk,
daniel@iogearbox.net
Subject: Re: 6ae81ced3788 ("af_packet: tone down the Tx-ring unsupported spew.")
Date: Thu, 12 Sep 2019 18:59:14 -0400 [thread overview]
Message-ID: <20190912225914.GF1546@sasha-vm> (raw)
In-Reply-To: <20190912192508.GA106326@google.com>
On Thu, Sep 12, 2019 at 12:25:10PM -0700, Zubin Mithra wrote:
>Hello,
>
>Syzkaller has triggered a WARNING in packet_set_ring when fuzzing a 4.4 kernel with the following stacktrace.
>Call Trace:
> __dump_stack lib/dump_stack.c:15 [inline]
> dump_stack+0xc1/0x124 lib/dump_stack.c:51
> panic+0x1a7/0x351 kernel/panic.c:115
> warn_slowpath_common+0x12a/0x140 kernel/panic.c:463
> warn_slowpath_fmt+0xb0/0xe0 kernel/panic.c:479
> packet_set_ring+0x13ed/0x19c0 net/packet/af_packet.c:4104
> packet_setsockopt+0x53e/0x21d0 net/packet/af_packet.c:3578
> SYSC_setsockopt net/socket.c:1766 [inline]
> SyS_setsockopt+0x15d/0x240 net/socket.c:1745
> entry_SYSCALL_64_fastpath+0x12/0x72
>
>
>Could the following patch be applied in v4.4.y? It is present in v4.9.y. Applying this patch could
>allow the fuzzer to explore more codepaths.
>* 6ae81ced3788 ("af_packet: tone down the Tx-ring unsupported spew.")
Queued up for 4.4, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-12 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 19:25 6ae81ced3788 ("af_packet: tone down the Tx-ring unsupported spew.") Zubin Mithra
2019-09-12 22:59 ` Sasha Levin [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=20190912225914.GF1546@sasha-vm \
--to=sashal@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davej@codemonkey.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=stable@vger.kernel.org \
--cc=zsm@chromium.org \
/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