linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mleitner@redhat.com
To: john.p.donnelly@oracle.com
Cc: linux-sctp@vger.kernel.org
Subject: Re: syzkaller test panic: Linux 5.4.y
Date: Tue, 19 Oct 2021 08:24:19 -0700	[thread overview]
Message-ID: <CALnP8ZZ7UbEzc0+VVpwucbBqNfgTqOk-LN8BwjbtL8-CbzOY6Q@mail.gmail.com> (raw)
In-Reply-To: <4f9d3a13-2104-ec1c-dbc7-12de1f99ea0e@oracle.com>

Hi John,

On Mon, Oct 18, 2021 at 04:29:58PM -0500, john.p.donnelly@oracle.com wrote:
>   Call Trace:
>    skb_put+0x4c/0x4c
>    sctp_addto_chunk+0x59/0xb0 [sctp]
>    sctp_make_strreset_req+0x166/0x180 [sctp]
>    sctp_send_reset_streams+0x14d/0x300 [sctp]
>    sctp_setsockopt.part.21+0x101f/0x1720 [sctp]
>    sctp_setsockopt+0x99/0xb0 [sctp]
>    sock_common_setsockopt+0x1a/0x1c
>    SyS_setsockopt+0x86/0xe6
>    +0x79/0x1ae
>    entry_SYSCALL_64_after_hwframe+0x151/0x0
>  RIP: 0033:0x7f80bdc21be9
>
>
> I am not familar with any of the sctp subsystem. It was found running the
> syzkaller fuzzing test suite.
>
> If there is a more appropriate place to report this I can do that too. This

Here is fine :)

> test fails on just about every 4.x and 5.x kernel.  It is not
> unique to 5.4.

Did the test kernels include commit "sctp: account stream padding
length for reconf chunk"? It is a recent fix right on this topic. It
should be fixed by it, actually.

  Marcelo


  reply	other threads:[~2021-10-19 15:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 21:29 syzkaller test panic: Linux 5.4.y john.p.donnelly
2021-10-19 15:24 ` mleitner [this message]
2021-10-19 20:05   ` john.p.donnelly
2021-10-19 21:35     ` Marcelo Ricardo Leitner
2021-10-19 21:41       ` john.p.donnelly
2021-10-20 15:12       ` john.p.donnelly

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=CALnP8ZZ7UbEzc0+VVpwucbBqNfgTqOk-LN8BwjbtL8-CbzOY6Q@mail.gmail.com \
    --to=mleitner@redhat.com \
    --cc=john.p.donnelly@oracle.com \
    --cc=linux-sctp@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).