linux-kernel.vger.kernel.org archive mirror
 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 fix for 5.6-rc2
Date: Mon, 17 Feb 2020 19:43:26 +0100	[thread overview]
Message-ID: <cover.1581962653.git.dsterba@suse.com> (raw)

Hi,

this is fix for sleeping in a locked section bug reported by Dave Jones,
caused by a patch dependence in development and pulled branches. I
picked the existing patch over the fixup that Filipe sent, as it's a
bit more generic fix. I've verified it with a specific test case, some rsync
stress and one round of fstests. Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 1b9867eb6120db85f8dca8ff42789d9ec9ee16a5:

  btrfs: sysfs, move device id directories to UUID/devinfo (2020-02-12 18:28:22 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.6-rc1-tag

for you to fetch changes up to 52e29e331070cd7d52a64cbf1b0958212a340e28:

  btrfs: don't set path->leave_spinning for truncate (2020-02-17 16:23:06 +0100)

----------------------------------------------------------------
Josef Bacik (1):
      btrfs: don't set path->leave_spinning for truncate

 fs/btrfs/inode.c | 2 --
 1 file changed, 2 deletions(-)

             reply	other threads:[~2020-02-17 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 18:43 David Sterba [this message]
2020-02-18  5:40 ` [GIT PULL] Btrfs fix for 5.6-rc2 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.1581962653.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).