From: Nikolay Borisov <nborisov@suse.com>
To: David Sterba <dsterba@suse.com>, clm@fb.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PULL] Btrfs for 4.13, part 1
Date: Wed, 28 Jun 2017 09:49:49 +0300 [thread overview]
Message-ID: <1ad1fcee-d7de-452d-3e9f-a87fe5d6117e@suse.com> (raw)
In-Reply-To: <cover.1498229425.git.dsterba@suse.com>
On 23.06.2017 18:16, David Sterba wrote:
> Hi,
>
> this is the main batch for 4.13. There are some user visible changes, see
> below. The core updates improve error handling (mostly related to bios), with
> the usual incremental work on the GFP_NOFS (mis)use removal. All patches have
> been in for-next for an extensive amount of time.
>
> Thre will be followups but I want push the series (111 patches) forward. There
> are also some updates to adjacent subsystems (writeback and blocklayer), so I
> want to give some stable point for merging in the upcoming weeks.
>
> User visible changes:
> * quota override tunable
> * improved compression thresholds
> * statx support
> * obsoleted mount option alloc_start
>
> Core updates:
> * bio-related updates
> - faster bio cloning
> - no allocation failures
> - preallocated flush bios
> * more kvzalloc use, memalloc_nofs protections, GFP_NOFS updates
> * prep work for btree_inode removal
> * dir-item validation
> * qgoup fixes and updates
> * cleanups
> - removed unused struct members, unused code, refactoring
> - argument refactoring (fs_info/root, caller -> callee sink)
> - SEARCH_TREE docs
>
> ----------------------------------------------------------------
> The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
>
> Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.13-part1
>
> for you to fetch changes up to f3f000297be88b1b75fde5027d660a8d8a44de14:
>
> btrfs: qgroup: Fix qgroup reserved space underflow by only freeing reserved ranges (2017-06-21 20:56:14 +0200)
>
Dave I run bisection of all failures between -rc6 and your
pull request and here are the results:
btrfs/048 - e79a33270d05 ("btrfs: Check name_len with boundary in verify dir_item")
btrfs/053 - b780e22768d3 ("btrfs: fix validation of XATTR_ITEM dir items")
generic/273 - 28785f70ef88 ("Btrfs: skip commit transaction if we don't have enough pinned bytes")
generic/337 - e79a33270d05 ("btrfs: Check name_len with boundary in verify dir_item")
shared/002 - e79a33270d05 ("btrfs: Check name_len with boundary in verify dir_item")
So those are tests which are failing as a direct of
the listed patches.
next prev parent reply other threads:[~2017-06-28 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 15:16 [PULL] Btrfs for 4.13, part 1 David Sterba
2017-06-24 10:05 ` Wang Shilong
2017-06-25 21:34 ` Jeff Mahoney
2017-06-26 0:53 ` Qu Wenruo
2017-06-26 1:46 ` Jeff Mahoney
2017-06-28 14:38 ` David Sterba
2017-06-28 14:28 ` David Sterba
2017-06-26 13:40 ` [PULL] Btrfs for 4.13, part 1 (update 1) David Sterba
2017-06-26 16:58 ` [PULL] Btrfs for 4.13, part 1 Chris Mason
2017-06-27 11:00 ` Filipe Manana
2017-06-28 15:39 ` David Sterba
2017-06-28 6:49 ` Nikolay Borisov [this message]
2017-06-30 7:44 ` David Sterba
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=1ad1fcee-d7de-452d-3e9f-a87fe5d6117e@suse.com \
--to=nborisov@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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).