From: David Howells <dhowells@redhat•com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail•com>
Cc: dhowells@redhat•com, Jakub Kicinski <kuba@kernel•org>,
syzbot <syzbot+f527b971b4bdc8e79f9e@syzkaller•appspotmail.com>,
bpf@vger•kernel.org, brauner@kernel•org, davem@davemloft•net,
dsahern@kernel•org, edumazet@google•com,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org, pabeni@redhat•com,
syzkaller-bugs@googlegroups•com, viro@zeniv•linux.org.uk
Subject: Re: Endless loop in udp with MSG_SPLICE_READ - Re: [syzbot] [fs?] INFO: task hung in pipe_release (4)
Date: Sun, 30 Jul 2023 18:32:58 +0100 [thread overview]
Message-ID: <810481.1690738378@warthog.procyon.org.uk> (raw)
In-Reply-To: <64c6672f580e3_11d0042944e@willemb.c.googlers.com.notmuch>
Willem de Bruijn <willemdebruijn.kernel@gmail•com> wrote:
> The syzkaller repro runs in threaded mode, so syscalls should not be
> interpreted in order.
I think they are actually ordered. It's kind of weirdly done, though,
flipping back and forth between threads and using futexes for synchronisation.
David
next prev parent reply other threads:[~2023-07-30 17:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000881d0606004541d1@google.com>
2023-07-12 18:54 ` [syzbot] [fs?] INFO: task hung in pipe_release (4) syzbot
2023-07-18 23:07 ` Jakub Kicinski
2023-07-28 23:52 ` David Howells
2023-07-29 15:27 ` David Howells
2023-07-29 21:49 ` Endless loop in udp with MSG_SPLICE_READ - " David Howells
2023-07-30 13:35 ` Willem de Bruijn
2023-07-30 14:30 ` Willem de Bruijn
2023-07-30 17:32 ` David Howells [this message]
2023-07-31 8:13 ` David Howells
2023-07-31 12:45 ` Willem de Bruijn
2023-07-31 13:34 ` David Howells
2023-08-01 12:40 ` David Howells
2023-08-01 12:58 ` Willem de Bruijn
2023-08-01 13:08 ` Willem de Bruijn
2023-08-01 14:01 ` David Howells
2023-08-01 14:02 ` David Howells
2023-08-01 14:19 ` David Howells
2023-08-01 14:31 ` Willem de Bruijn
2023-08-01 14:47 ` David Howells
2023-08-01 14:59 ` Willem de Bruijn
2023-07-24 13:17 ` David Howells
2023-08-02 13:21 ` David Howells
2023-08-02 16:48 ` syzbot
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=810481.1690738378@warthog.procyon.org.uk \
--to=dhowells@redhat$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=brauner@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=syzbot+f527b971b4bdc8e79f9e@syzkaller$(echo .)appspotmail.com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=willemdebruijn.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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