From: David Howells <dhowells@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: dhowells@redhat.com, David Hildenbrand <david@redhat.com>,
syzbot <syzbot+a440341a59e3b7142895@syzkaller.appspotmail.com>,
hch@lst.de, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in skb_dequeue (3)
Date: Fri, 03 Feb 2023 08:36:10 +0000 [thread overview]
Message-ID: <1723030.1675413370@warthog.procyon.org.uk> (raw)
In-Reply-To: <72029a93-1150-1994-916f-b15ef0befd49@nvidia.com>
Interestingly, the problem also goes away if the ftruncate is removed from the
test program.
Are pages ever spliced from the pipe directly into the pagecache on both xfs
and ext4? I'm not sure whether that could happen as the test seeks 2048 bytes
in before doing the sendfile().
David
next prev parent reply other threads:[~2023-02-03 8:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 10:04 syzbot
2023-02-02 8:52 ` David Howells
2023-02-02 9:02 ` David Hildenbrand
2023-02-02 15:15 ` David Howells
2023-02-03 2:54 ` John Hubbard
2023-02-03 8:36 ` David Howells [this message]
2023-02-03 14:36 ` David Howells
2023-02-03 16:23 ` David Howells
2023-02-03 16:27 ` How does ftruncate() interact with DIO read? David Howells
2023-02-03 16:31 ` Christoph Hellwig
2023-02-03 16:30 ` [syzbot] general protection fault in skb_dequeue (3) David Howells
2023-02-02 23:10 ` John Hubbard
2023-02-07 11:22 ` David Howells
2023-02-07 12:29 ` syzbot
[not found] <20230201115301.463-1-hdanton@sina.com>
2023-02-01 15:15 ` syzbot
[not found] <20230201233913.650-1-hdanton@sina.com>
2023-02-02 5:53 ` syzbot
[not found] <20230207095807.1448-1-hdanton@sina.com>
2023-02-07 10:24 ` 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=1723030.1675413370@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+a440341a59e3b7142895@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
all inboxes | Powered by JetHome®