linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Pagecache fixes for 5.19-rc4
Date: Thu, 23 Jun 2022 17:42:40 +0100	[thread overview]
Message-ID: <YrSYAKtoRrrgayrZ@casper.infradead.org> (raw)

The following changes since commit 78ca55889a549a9a194c6ec666836329b774ab6d:

  Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2022-06-20 09:35:04 -0500)

are available in the Git repository at:

  git://git.infradead.org/users/willy/pagecache.git tags/folio-5.19b

for you to fetch changes up to 00fa15e0d56482e32d8ca1f51d76b0ee00afb16b:

  filemap: Fix serialization adding transparent huge pages to page cache (2022-06-23 12:22:00 -0400)

----------------------------------------------------------------
Four folio-related fixes for 5.19:

 - Mark a folio accessed at the right time (Yu Kuai)

 - Fix a race for folios being replaced in the middle of a read (Brian Foster)

 - Clear folio->private in more places (Xiubo Li)

 - Take the invalidate_lock in page_cache_ra_order() (Alistair Popple)

----------------------------------------------------------------
Alistair Popple (1):
      filemap: Fix serialization adding transparent huge pages to page cache

Matthew Wilcox (Oracle) (3):
      filemap: Correct the conditions for marking a folio as accessed
      filemap: Handle sibling entries in filemap_get_read_batch()
      mm: Clear page->private when splitting or migrating a page

 mm/filemap.c     | 15 ++++++++++++---
 mm/huge_memory.c |  1 +
 mm/migrate.c     |  1 +
 mm/readahead.c   |  2 ++
 4 files changed, 16 insertions(+), 3 deletions(-)



             reply	other threads:[~2022-06-23 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 16:42 Matthew Wilcox [this message]
2022-06-23 17:19 ` pr-tracker-bot

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=YrSYAKtoRrrgayrZ@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.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