From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: syzbot <syzbot+3dcd59a1f907245f891f@syzkaller.appspotmail.com>,
ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, Xin Long <lucien.xin@gmail.com>
Subject: Re: INFO: rcu detected stall in is_bpf_text_address
Date: Sat, 19 May 2018 22:45:44 -0300 [thread overview]
Message-ID: <20180520014544.GB26212@localhost.localdomain> (raw)
In-Reply-To: <4b65142a-cf3b-05d7-d66b-018ff8da7ccc@gmail.com>
On Sat, May 19, 2018 at 08:57:19AM -0700, Eric Dumazet wrote:
> SCTP experts, please take a look.
Ugh, same sctp footprint as in the other reports.
>
> > _sctp_make_chunk+0x58/0x280 net/sctp/sm_make_chunk.c:1417
> > sctp_make_control net/sctp/sm_make_chunk.c:1464 [inline]
> > sctp_make_heartbeat+0x8f/0x430 net/sctp/sm_make_chunk.c:1177
> > sctp_sf_heartbeat.isra.23+0x26/0x180 net/sctp/sm_statefuns.c:1005
> > sctp_sf_sendbeat_8_3+0x38e/0x550 net/sctp/sm_statefuns.c:1049
> > sctp_do_sm+0x1ab/0x7160 net/sctp/sm_sideeffect.c:1188
> > sctp_generate_heartbeat_event+0x218/0x450 net/sctp/sm_sideeffect.c:406
> > call_timer_fn+0x230/0x940 kernel/time/timer.c:1326
> > expire_timers kernel/time/timer.c:1363 [inline]
> > __run_timers+0x79e/0xc50 kernel/time/timer.c:1666
> > run_timer_softirq+0x4c/0x70 kernel/time/timer.c:1692
next prev parent reply other threads:[~2018-05-20 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 15:55 INFO: rcu detected stall in is_bpf_text_address syzbot
2018-05-19 15:57 ` Eric Dumazet
2018-05-20 1:45 ` Marcelo Ricardo Leitner [this message]
2018-05-20 8:26 ` Xin Long
2018-05-22 0:43 ` Marcelo Ricardo Leitner
2018-05-28 17:55 ` Marcelo Ricardo Leitner
2018-05-28 18:22 ` Marcelo Ricardo Leitner
2018-05-29 11:53 ` Andrey Konovalov
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=20180520014544.GB26212@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+3dcd59a1f907245f891f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).