From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, Jens Axboe <axboe@kernel.dk>,
Ayush Jain <ayush.jain3@amd.com>,
broonie@kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Santosh.Shukla@amd.com, Kalpana.Shetty@amd.com,
Narasimhan V <Narasimhan.V@amd.com>,
sfr@canb.auug.org.au
Subject: Re: linux-next: Tree for Apr 13
Date: Mon, 17 Apr 2023 15:06:47 +0100 [thread overview]
Message-ID: <1558440.1681740407@warthog.procyon.org.uk> (raw)
In-Reply-To: <1551344.1681739138@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> The problem might be summed up by the following snippet:
>
> openat(AT_FDCWD, "/dev/loop0", O_RDONLY) = 3
> newfstatat(3, "", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x7, 0), ...}, AT_EMPTY_PATH) = 0
> splice(3, NULL, 1, NULL, 1048576, 0) = 0
Ah. In filemap_splice_read():
do {
cond_resched();
if (*ppos >= i_size_read(file_inode(in)))
break;
but i_size_read(file_inode(in)) for a blockdev returns 0, it would seem. What
should I use instead?
David
next prev parent reply other threads:[~2023-04-17 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 18:25 linux-next: Tree for Apr 13 broonie
2023-04-14 5:11 ` Jain, Ayush
2023-04-14 7:25 ` Ayush Jain
2023-04-15 20:37 ` Jens Axboe
2023-04-17 12:28 ` David Howells
2023-04-17 13:45 ` David Howells
2023-04-17 14:06 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-13 15:56 Mark Brown
2022-04-13 5:25 Stephen Rothwell
2021-04-13 10:04 Stephen Rothwell
2020-04-13 2:18 Stephen Rothwell
2018-04-13 3:13 Stephen Rothwell
2017-04-13 5:38 Stephen Rothwell
2016-04-13 5:05 Stephen Rothwell
2015-04-13 12:12 Stephen Rothwell
2012-04-13 5:31 Stephen Rothwell
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=1558440.1681740407@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Kalpana.Shetty@amd.com \
--cc=Narasimhan.V@amd.com \
--cc=Santosh.Shukla@amd.com \
--cc=axboe@kernel.dk \
--cc=ayush.jain3@amd.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.