All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs update, part 2
Date: Wed, 10 Nov 2021 18:38:09 +0100	[thread overview]
Message-ID: <cover.1636564333.git.dsterba@suse.com> (raw)

Hi,

here's a separate fix that depends on changes that landed last week (the
iomap + iov_iter merged as c03098d4b9ad).

The fix itself is for a deadlock when direct/buffered IO is done on a
mmaped file and a fault happens (details in the patch). There's a fstest
generic/647 that triggers the problem and makes testing hard.

No merge conflicts. Please pull, thanks.

----------------------------------------------------------------
The following changes since commit c03098d4b9ad76bca2966a8769dcfe59f7f85103:

  Merge tag 'gfs2-v5.15-rc5-mmap-fault' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2021-11-02 12:25:03 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.16-deadlock-fix-tag

for you to fetch changes up to 51bd9563b6783de8315f38f7baed949e77c42311:

  btrfs: fix deadlock due to page faults during direct IO reads and writes (2021-11-09 13:46:07 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: fix deadlock due to page faults during direct IO reads and writes

 fs/btrfs/file.c | 139 +++++++++++++++++++++++++++++++++++++++++++++++++-------
 1 file changed, 123 insertions(+), 16 deletions(-)

             reply	other threads:[~2021-11-10 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 17:38 David Sterba [this message]
2021-11-11  1:07 ` [GIT PULL] Btrfs update, part 2 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=cover.1636564333.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.