From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: akpm@linux-foundation.org, jack@suse.cz, kirill@shutemov.name
Cc: borntraeger@de.ibm.com, david@redhat.com, aarcange@redhat.com,
linux-mm@kvack.org, frankja@linux.ibm.com, sfr@canb.auug.org.au,
jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, dave.hansen@intel.com,
peterz@infradead.org, sean.j.christopherson@intel.com
Subject: [PATCH v1 1/1] fs/splice: add missing callback for inaccessible pages
Date: Wed, 29 Apr 2020 00:50:43 +0200 [thread overview]
Message-ID: <20200428225043.3091359-1-imbrenda@linux.ibm.com> (raw)
If a page is inaccesible and it is used for things like sendfile, then
the content of the page is not always touched, and can be passed
directly to a driver, causing issues.
This patch fixes the issue by adding a call to arch_make_page_accessible
in page_cache_pipe_buf_confirm; this fixes the issue.
Fixes: f28d43636d6f ("mm/gup/writeback: add callbacks for inaccessible pages")
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
---
fs/splice.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/splice.c b/fs/splice.c
index 4735defc46ee..f026e0ce9acd 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -106,6 +106,9 @@ static int page_cache_pipe_buf_confirm(struct pipe_inode_info *pipe,
struct page *page = buf->page;
int err;
+ if (arch_make_page_accessible(page))
+ return -EIO;
+
if (!PageUptodate(page)) {
lock_page(page);
--
2.25.4
next reply other threads:[~2020-04-28 22:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 22:50 Claudio Imbrenda [this message]
2020-04-29 0:25 ` Dave Hansen
2020-04-29 16:07 ` Dave Hansen
2020-04-29 17:31 ` Christian Borntraeger
2020-04-29 17:55 ` Dave Hansen
2020-04-29 22:53 ` Claudio Imbrenda
2020-04-29 23:52 ` Dave Hansen
2020-04-30 17:19 ` Claudio Imbrenda
2020-04-30 17:30 ` Dave Hansen
2020-04-30 18:12 ` Christian Borntraeger
2020-04-30 19:02 ` Christian Borntraeger
2020-04-30 19:54 ` Christian Borntraeger
2020-04-30 22:26 ` John Hubbard
2020-04-30 19:32 ` Dave Hansen
2020-04-30 19:38 ` Christian Borntraeger
2020-04-30 20:01 ` Dave Hansen
2020-04-30 20:03 ` Christian Borntraeger
2020-04-30 19:45 ` Christian Borntraeger
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=20200428225043.3091359-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox