linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Chris Mason <clm@fb.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL] Btrfs, updates for 4.12
Date: Wed, 26 Apr 2017 18:08:08 +0200	[thread overview]
Message-ID: <20170426160808.GB23260@suse.cz> (raw)
In-Reply-To: <CAL3q7H6dNZ1SShz6iaHYeqMQ+PCAKPzetMuRm+8MVA-8h2E0MA@mail.gmail.com>

On Wed, Apr 26, 2017 at 04:06:29PM +0100, Filipe Manana wrote:
> On Wed, Apr 19, 2017 at 12:35 PM, David Sterba <dsterba@suse.com> wrote:
> > Adam Borowski (1):
> >       btrfs: fix a bogus warning when converting only data or metadata
> >
> > Anand Jain (3):
> >       btrfs: use q which is already obtained from bdev_get_queue
> >       btrfs: delete unused member nobarriers
> >       btrfs: check if the device is flush capable
> >
> > Dan Carpenter (1):
> >       Btrfs: handle only applicable errors returned by btrfs_get_extent
> >
> > David Sterba (12):
> >       btrfs: preallocate radix tree node for readahead
> >       btrfs: preallocate radix tree node for global readahead tree
> >       btrfs: remove redundant parameter from btree_readahead_hook
> >       btrfs: remove redundant parameter from reada_find_zone
> >       btrfs: remove redundant parameter from reada_start_machine_dev
> >       btrfs: remove local blocksize variable in reada_find_extent
> >       btrfs: remove unused qgroup members from btrfs_trans_handle
> >       btrfs: track exclusive filesystem operation in flags
> >       btrfs: sink GFP flags parameter to tree_mod_log_insert_move
> >       btrfs: sink GFP flags parameter to tree_mod_log_insert_root
> >       btrfs: drop redundant parameters from btrfs_map_sblock
> >       btrfs: use clear_page where appropriate
> 
> Did you actually ran xfstests with those readahead patches to
> preallocate radix tree nodes?
> 
> With those 2 patches applied (Chris' for-linus.4,12 branch) this
> breaks things and many btrfs specific tests (at least, since I can't
> get pass them) result in tons of traces like the following in a debug
> kernel:

I did, no such reports appeared in my setup. There are several debugging
options enabled in the config but I don't see the one to catch sleep in
atomic. I'll fix my setup scripts to enable it before each build. There
might be other surprises that I missed though. Thanks for cathing it.

  parent reply	other threads:[~2017-04-26 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 11:35 [PULL] Btrfs, updates for 4.12 David Sterba
2017-04-26 15:06 ` Filipe Manana
2017-04-26 15:12   ` Chris Mason
2017-04-26 16:08   ` David Sterba [this message]
2017-04-26 17:26   ` Chris Mason

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=20170426160808.GB23260@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=fdmanana@gmail.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).