mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Jan Kara <jack@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zi Yan <ziy@nvidia.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Nico Pache <nico.pache@linux.dev>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
	Usama Arif <usama.arif@linux.dev>,
	Kiryl Shutsemau <kas@kernel.org>,
	Matthew Brost <matthew.brost@intel.com>,
	Joshua Hahn <joshua.hahnjy@gmail.com>,
	Byungchul Park <byungchul@sk.com>,
	Gregory Price <gourry@gourry.net>,
	Ying Huang <ying.huang@linux.alibaba.com>,
	Alistair Popple <apopple@nvidia.com>,
	Peter Xu <peterx@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Song Liu <songliubraving@fb.com>, Rik van Riel <riel@surriel.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>,
	Hugh Dickins <hughd@google.com>, Will Deacon <will@kernel.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
	Nick Piggin <npiggin@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	Kevin Tian <kevin.tian@intel.com>,
	"Joerg Roedel (AMD)" <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Steve Sistare <steven.sistare@oracle.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Josef Bacik <josef@toxicpanda.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, fuse-devel@lists.linux.dev,
	linux-arch@vger.kernel.org, iommu@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH v2 2/5] mm: limit pagecache folio refcount when splicing into pipes
Date: Mon, 9 Nov 2026 10:49:08 +0100	[thread overview]
Message-ID: <43fc45ff-8636-4961-a80a-29844c15d7a1@kernel.org> (raw)
In-Reply-To: <8d23b1eb-72aa-479d-9486-dbfd86d8414c@kernel.org>

On 11/9/26 10:30, David Hildenbrand (Arm) wrote:
> On 11/9/26 09:57, Jose A. Perez de Azpillaga wrote:
>> On 11/7/26 11:23 PM, David Hildenbrand (Arm) wrote:
>>> Similar to mapping pagecache folios into page tables, let's reject
>>> additional references when splicing folios into a pipe if the refcount
>>> is at its limit, similar to how we handle it during GUP.
>>>
>>> This will prevent more cases of possible folio refcount overflows with
>>> large pagecache folios.
>>>
>>> Let's keep it simple and check in the two callers of
>>> splice_folio_into_pipe(). Return -EOVERFLOW if the limit prevents any
>>> progress, so do_splice_read() can fall back to copy_splice_read() when
>>> read_iter is available. This keeps sendfile() and other splice users
>>> working when ordinary reads would still succeed.
>>>
>>> Also fall back to copying in FUSE when taking another reference through
>>> fuse_ref_folio() would exceed the limit.
>>>
>>> Also check in try_get_page() to cover pipe-buffer duplication by tee()
>>> and partial pipe-to-pipe splicing.
>>>
>>> Fixes: 800d8c63b2e9 ("shmem: add huge pages support")
>>> Fixes: 99cb0dbd47a1 ("mm,thp: add read-only THP support for (non-shmem) FS")
>>> Fixes: 793917d997df ("mm/readahead: Add large folio readahead")
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>>> ---
>>>  fs/fuse/dev.c      |  5 +++--
>>>  fs/splice.c        |  8 +++++++-
>>>  include/linux/mm.h |  9 ++++++---
>>>  mm/filemap.c       | 11 ++++++++---
>>>  mm/shmem.c         |  4 ++++
>>>  5 files changed, 28 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
>>> index 3641abb90d6bb..4f6b7b42bfd3e 100644
>>> --- a/fs/fuse/dev.c
>>> +++ b/fs/fuse/dev.c
>>> @@ -1265,9 +1265,10 @@ int fuse_copy_folio(struct fuse_copy_state *cs, struct folio **foliop,
>>>  		if (cs->write && cs->pipebufs && folio) {
>>>  			/*
>>>  			 * Can't control lifetime of pipe buffers, so always
>>> -			 * copy user pages.
>>> +			 * copy user pages. Also copy folios at their refcount limit.
>>>  			 */
>>> -			if (cs->req->args->user_pages) {
>>> +			if (cs->req->args->user_pages ||
>>> +			    unlikely(folio_ref_count_over_limit(folio))) {
>>>  				err = fuse_copy_fill(cs);
>>>  				if (err)
>>>  					return err;
>>> diff --git a/fs/splice.c b/fs/splice.c
>>> index e6d43329ed3f0..df73a4e65118b 100644
>>> --- a/fs/splice.c
>>> +++ b/fs/splice.c
>>> @@ -956,6 +956,7 @@ static ssize_t do_splice_read(struct file *in, loff_t *ppos,
>>>  			      unsigned int flags)
>>>  {
>>>  	unsigned int p_space;
>>> +	ssize_t ret;
>>>  
>>>  	if (unlikely(!(in->f_mode & FMODE_READ)))
>>>  		return -EBADF;
>>> @@ -977,7 +978,12 @@ static ssize_t do_splice_read(struct file *in, loff_t *ppos,
>>>  	 */
>>>  	if ((in->f_flags & O_DIRECT) || IS_DAX(in->f_mapping->host))
>>>  		return copy_splice_read(in, ppos, pipe, len, flags);
>>> -	return in->f_op->splice_read(in, ppos, pipe, len, flags);
>>> +	ret = in->f_op->splice_read(in, ppos, pipe, len, flags);
>>> +
>>> +	/* Fallback to copying when hitting folio refcount limits. */
>>> +	if (unlikely(ret == -EOVERFLOW) && in->f_op->read_iter)
>>> +		ret = copy_splice_read(in, ppos, pipe, len, flags);
>>
>> here it can't tell where the -EOVERFLOW came from, if another file
>> returns -EOVERFLOW (i.e. tty_fops uses copy_splice_read, and
>> n_hdlc_tty_read() returns -EOVERFLOW after dropping the frame), it now
>> gets a second read.
> 
> 
> That's what claude told me during review, and when asked whether that actually
> happened in practice it said no ;)
> 
> So is that actually a problem?

Double checked, claude managed to confuse itself.

n_hdlc_tty_read() can indeed return -EOVERFLOW.

I should just have let splice keep failing, dealing with copy fallback starts to
get annoying.

I guess switching to -ETOOMANYREFS should work (and might be a better fitting error)

-- 
Cheers,

David


  reply	other threads:[~2026-11-09  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 22:23 [PATCH v2 0/5] mm: limit pagecache folio refcount David Hildenbrand (Arm)
2026-11-07 22:23 ` [PATCH v2 1/5] mm: limit pagecache folio refcount when mapping pages David Hildenbrand (Arm)
2026-11-09  8:35   ` Jose A. Perez de Azpillaga
2026-11-07 22:23 ` [PATCH v2 2/5] mm: limit pagecache folio refcount when splicing into pipes David Hildenbrand (Arm)
2026-11-09  8:57   ` Jose A. Perez de Azpillaga
2026-11-09  9:30     ` David Hildenbrand (Arm)
2026-11-09  9:49       ` David Hildenbrand (Arm) [this message]
2026-11-09 10:07         ` Jose A. Perez de Azpillaga
2026-11-09 10:08         ` David Hildenbrand (Arm)
2026-11-07 22:23 ` [PATCH v2 3/5] mm/mmu_gather: flush pending references early before the folio limit David Hildenbrand (Arm)
2026-11-07 22:23 ` [PATCH v2 4/5] iommufd: fix cleanup when adding memfd folio pins fails David Hildenbrand (Arm)
2026-11-07 22:23 ` [PATCH v2 5/5] mm/gup: limit pagecache folio refcount when grabbing references David Hildenbrand (Arm)
2026-11-09  9:05   ` Jose A. Perez de Azpillaga

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=43fc45ff-8636-4961-a80a-29844c15d7a1@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@kernel.org \
    --cc=apopple@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=azpijr@gmail.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=byungchul@sk.com \
    --cc=dev.jain@arm.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=gourry@gourry.net \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=jack@suse.cz \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=josef@toxicpanda.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kas@kernel.org \
    --cc=kevin.tian@intel.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=mhocko@suse.com \
    --cc=miklos@szeredi.hu \
    --cc=nico.pache@linux.dev \
    --cc=npiggin@gmail.com \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=songliubraving@fb.com \
    --cc=stable@vger.kernel.org \
    --cc=steven.sistare@oracle.com \
    --cc=surenb@google.com \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=ying.huang@linux.alibaba.com \
    --cc=ziy@nvidia.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®