All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: [GIT PULL] Rare page cache data corruption fix
Date: Fri, 22 Apr 2022 20:45:35 +0100	[thread overview]
Message-ID: <YmMF32RlCn2asAhc@casper.infradead.org> (raw)

Syzbot found a nasty race between large page splitting and page lookup.
Details in the commit log, but fortunately it has a reliable reproducer.
I thought it better to send this one to you straight away.

The other commit fixes the test suite build, again.

The following changes since commit 281b9d9a4b02229b602a14f7540206b0fbe4134f:

  Merge branch 'akpm' (patches from Andrew) (2022-04-22 10:10:43 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/willy/xarray.git tags/xarray-5.18a

for you to fetch changes up to 63b1898fffcd8bd81905b95104ecc52b45a97e21:

  XArray: Disallow sibling entries of nodes (2022-04-22 15:35:40 -0400)

----------------------------------------------------------------
XArray: Two fixes for 5.18

 - Fix the test suite build for kmem_cache_alloc_lru()

 - Fix a rare race between split and load

----------------------------------------------------------------
Matthew Wilcox (Oracle) (2):
      tools: Add kmem_cache_alloc_lru()
      XArray: Disallow sibling entries of nodes

 lib/xarray.c                     | 2 ++
 tools/include/linux/slab.h       | 8 +++++++-
 tools/testing/radix-tree/linux.c | 3 ++-
 3 files changed, 11 insertions(+), 2 deletions(-)


             reply	other threads:[~2022-04-22 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 19:45 Matthew Wilcox [this message]
2022-04-22 20:35 ` [GIT PULL] Rare page cache data corruption fix Linus Torvalds
2022-04-22 20:46 ` pr-tracker-bot
2022-04-30 19:22 ` Andrew Morton

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=YmMF32RlCn2asAhc@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 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.