Linux-BTRFS Archive on lore.kernel.org
 help / color / 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 fixes for 5.4-rc7
Date: Sat,  9 Nov 2019 16:07:16 +0100
Message-ID: <cover.1573307154.git.dsterba@suse.com> (raw)

Hi,

there are a few regressions and fixes for stable. Please pull, thanks.

Regressions:

- fix a race leading to metadata space leak after task received a signal

- un-deprecate 2 ioctls, marked as deprecated by mistake

Fixes:

- fix limit check for number of devices during chunk allocation

- fix a race due to double evaluation of i_size_read inside max() macro,
  can cause a crash

- remove wrong device id check in tree-checker

----------------------------------------------------------------
The following changes since commit ba0b084ac309283db6e329785c1dc4f45fdbd379:

  Btrfs: check for the full sync flag while holding the inode lock during fsync (2019-10-17 20:36:02 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.4-rc6-tag

for you to fetch changes up to a5009d3a318e9f02ddc9aa3d55e2c64d6285c4b9:

  btrfs: un-deprecate ioctls START_SYNC and WAIT_SYNC (2019-11-04 21:42:01 +0100)

----------------------------------------------------------------
David Sterba (1):
      btrfs: un-deprecate ioctls START_SYNC and WAIT_SYNC

Filipe Manana (1):
      Btrfs: fix race leading to metadata space leak after task received signal

Josef Bacik (1):
      btrfs: save i_size to avoid double evaluation of i_size_read in compress_file_range

Qu Wenruo (2):
      btrfs: Consider system chunk array size for new SYSTEM chunks
      btrfs: tree-checker: Fix wrong check on max devid

 fs/btrfs/inode.c        | 15 ++++++++++++++-
 fs/btrfs/ioctl.c        |  6 ------
 fs/btrfs/space-info.c   | 21 +++++++++++++++++++++
 fs/btrfs/tree-checker.c |  8 --------
 fs/btrfs/volumes.c      |  1 +
 5 files changed, 36 insertions(+), 15 deletions(-)

             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 15:07 David Sterba [this message]
2019-11-09 17:15 ` pr-tracker-bot

Reply instructions:

You may reply publically 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.1573307154.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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git