From: David Howells <dhowells@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>
Cc: David Howells <dhowells@redhat.com>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Logan Gunthorpe <logang@deltatee.com>,
Hillf Danton <hdanton@sina.com>,
Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
John Hubbard <jhubbard@nvidia.com>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH v19 10/15] iomap: Don't get an reference on ZERO_PAGE for direct I/O block zeroing
Date: Wed, 15 Mar 2023 16:35:44 +0000 [thread overview]
Message-ID: <20230315163549.295454-11-dhowells@redhat.com> (raw)
In-Reply-To: <20230315163549.295454-1-dhowells@redhat.com>
ZERO_PAGE can't go away, no need to hold an extra reference.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
cc: Al Viro <viro@zeniv.linux.org.uk>
cc: linux-fsdevel@vger.kernel.org
---
fs/iomap/direct-io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/iomap/direct-io.c b/fs/iomap/direct-io.c
index f771001574d0..850fb9870c2f 100644
--- a/fs/iomap/direct-io.c
+++ b/fs/iomap/direct-io.c
@@ -202,7 +202,7 @@ static void iomap_dio_zero(const struct iomap_iter *iter, struct iomap_dio *dio,
bio->bi_private = dio;
bio->bi_end_io = iomap_dio_bio_end_io;
- get_page(page);
+ bio_set_flag(bio, BIO_NO_PAGE_REF);
__bio_add_page(bio, page, len, 0);
iomap_dio_submit_bio(iter, dio, bio, pos);
}
next prev parent reply other threads:[~2023-03-15 16:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:35 [PATCH v19 00/15] splice, block: Use page pinning and kill ITER_PIPE David Howells
2023-03-15 16:35 ` [PATCH v19 01/15] splice: Clean up direct_splice_read() a bit David Howells
2023-03-15 18:58 ` David Hildenbrand
2023-03-15 16:35 ` [PATCH v19 02/15] splice: Make do_splice_to() generic and export it David Howells
2023-03-15 18:59 ` David Hildenbrand
2023-03-15 16:35 ` [PATCH v19 03/15] shmem: Implement splice-read David Howells
2023-03-15 16:35 ` [PATCH v19 04/15] overlayfs: " David Howells
2023-03-16 10:47 ` Christian Brauner
2023-03-16 13:14 ` David Hildenbrand
2023-03-15 16:35 ` [PATCH v19 05/15] coda: " David Howells
2023-03-15 16:35 ` [PATCH v19 06/15] tty, proc, kernfs, random: Use direct_splice_read() David Howells
2023-03-15 16:35 ` [PATCH v19 07/15] splice: Do splice read from a file without using ITER_PIPE David Howells
2023-03-16 10:43 ` Christian Brauner
2023-03-15 16:35 ` [PATCH v19 08/15] cifs: Use generic_file_splice_read() David Howells
2023-03-15 16:35 ` [PATCH v19 09/15] iov_iter: Kill ITER_PIPE David Howells
2023-03-16 10:51 ` Christian Brauner
2023-03-15 16:35 ` David Howells [this message]
2023-03-15 16:35 ` [PATCH v19 11/15] block: Fix bio_flagged() so that gcc can better optimise it David Howells
2023-03-15 16:35 ` [PATCH v19 12/15] block: Replace BIO_NO_PAGE_REF with BIO_PAGE_REFFED with inverted logic David Howells
2023-03-15 16:35 ` [PATCH v19 13/15] block: Add BIO_PAGE_PINNED and associated infrastructure David Howells
2023-03-15 16:35 ` [PATCH v19 14/15] block: Convert bio_iov_iter_get_pages to use iov_iter_extract_pages David Howells
2023-03-15 16:35 ` [PATCH v19 15/15] block: convert bio_map_user_iov " David Howells
2023-03-15 17:00 ` [PATCH v19 00/15] splice, block: Use page pinning and kill ITER_PIPE Linus Torvalds
2023-03-15 17:47 ` Jens Axboe
2023-03-20 13:10 ` Christoph Hellwig
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=20230315163549.295454-11-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=jlayton@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).