On Wed, Apr 26, 2017 at 04:06:29PM +0100, Filipe Manana wrote:
> On Wed, Apr 19, 2017 at 12:35 PM, David Sterba <dste...@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.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to