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>,
	clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.3-rc5
Date: Sun, 18 Aug 2019 13:58:46 +0200	[thread overview]
Message-ID: <cover.1566128979.git.dsterba@suse.com> (raw)

Hi,

please pull two fixes that pop during testing:

* fix for sysfs-related code that adds/removes block groups, warnings
  appear during several fstests in connection with sysfs updates in 5.3,
  the fix essentially replaces a workaround with scope NOFS and applies
  to 5.2-based branch too

* add sanity check of trim range

Thanks.

----------------------------------------------------------------
The following changes since commit a6d155d2e363f26290ffd50591169cb96c2a609e:

  Btrfs: fix deadlock between fiemap and transaction commits (2019-07-30 18:25:12 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.3-rc4-tag

for you to fetch changes up to 07301df7d2fc220d3de5f7ad804dcb941400cb00:

  btrfs: trim: Check the range passed into to prevent overflow (2019-08-07 16:42:39 +0200)

----------------------------------------------------------------
Filipe Manana (1):
      Btrfs: fix sysfs warning and missing raid sysfs directories

Qu Wenruo (1):
      btrfs: trim: Check the range passed into to prevent overflow

 fs/btrfs/ctree.h       |  4 ---
 fs/btrfs/disk-io.c     |  2 --
 fs/btrfs/extent-tree.c | 71 +++++++++++++++++++++++++-------------------------
 fs/btrfs/volumes.c     | 13 ---------
 4 files changed, 35 insertions(+), 55 deletions(-)

             reply	other threads:[~2019-08-18 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 11:58 David Sterba [this message]
2019-08-18 16:55 ` [GIT PULL] Btrfs fixes for 5.3-rc5 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.1566128979.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.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.