From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org, clm@fb.com
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] More GFP_NOFS removals
Date: Mon, 13 Feb 2017 14:50:04 +0100 [thread overview]
Message-ID: <cover.1486993643.git.dsterba@suse.com> (raw)
A few more conversions to less strict allocation flags, calls originating from
an ioctl and with no chance of getting back with a lock already held. For 4.11.
The following changes since commit 2e94257a41fece589dc4bd737c70dc770e9040ef:
btrfs: Better csum error message for data csum mismatch (2017-02-10 18:04:51 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/less-nofs
for you to fetch changes up to 8d310939a7d232fc71524fdf83f5a8fdbd5eb31c:
btrfs: use GFP_KERNEL in btrfs_add/del_qgroup_relation (2017-02-13 13:11:29 +0100)
----------------------------------------------------------------
David Sterba (4):
btrfs: use GFP_KERNEL in create_snapshot
btrfs: use GFP_KERNEL in btrfs_read_qgroup_config
btrfs: use GFP_KERNEL in btrfs_quota_enable
btrfs: use GFP_KERNEL in btrfs_add/del_qgroup_relation
fs/btrfs/ioctl.c | 4 ++--
fs/btrfs/qgroup.c | 8 ++++----
2 files changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2017-02-13 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 13:50 David Sterba [this message]
2017-02-13 13:50 ` [PATCH 1/4] btrfs: use GFP_KERNEL in create_snapshot David Sterba
2017-02-13 13:50 ` [PATCH 2/4] btrfs: use GFP_KERNEL in btrfs_read_qgroup_config David Sterba
2017-02-13 13:50 ` [PATCH 3/4] btrfs: use GFP_KERNEL in btrfs_quota_enable David Sterba
2017-02-13 13:50 ` [PATCH 4/4] btrfs: use GFP_KERNEL in btrfs_add/del_qgroup_relation 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=cover.1486993643.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.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).