From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, clm@fb.com
Subject: [PULL][PATCH 0/3] GFP flags adjustments
Date: Thu, 3 Dec 2015 17:51:48 +0100 [thread overview]
Message-ID: <cover.1449160585.git.dsterba@suse.com> (raw)
Part of the planned memory allocation / error handling updates, a lightweight
start. We don't need to use GFP_NOFS everywhere, this flag should protect
against looping back to the filesystem in certain allocation contexts. GFP_KERNEL
is safe in functions started eg. from userspace (like the ioctls) or for
mount-time allocations. For 4.5, please pull.
----------------------------------------------------------------
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/gfp-flags
for you to fetch changes up to 39a27ec1004e886f1d949bdb8f2616896d02c5c2:
btrfs: use GFP_KERNEL for xattr and acl allocations (2015-12-03 15:03:44 +0100)
----------------------------------------------------------------
David Sterba (3):
btrfs: use GFP_KERNEL for allocations in ioctl handlers
btrfs: use GFP_KERNEL for allocations of workqueues
btrfs: use GFP_KERNEL for xattr and acl allocations
fs/btrfs/acl.c | 4 ++--
fs/btrfs/async-thread.c | 4 ++--
fs/btrfs/ioctl.c | 10 +++++-----
fs/btrfs/xattr.c | 2 +-
4 files changed, 10 insertions(+), 10 deletions(-)
next reply other threads:[~2015-12-03 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 16:51 David Sterba [this message]
2015-12-03 16:51 ` [PATCH 1/3] btrfs: use GFP_KERNEL for allocations in ioctl handlers David Sterba
2015-12-03 16:51 ` [PATCH 2/3] btrfs: use GFP_KERNEL for allocations of workqueues David Sterba
2015-12-03 16:51 ` [PATCH 3/3] btrfs: use GFP_KERNEL for xattr and acl allocations 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.1449160585.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.