GFP flags adjustments, part 2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | btrfs: send: use GFP_KERNEL everywherefs/ | +18 | 0 replies | |
| 2/3 | btrfs: reada: use GFP_KERNEL everywherefs/ | +5 | 0 replies | |
| 3/3 | btrfs: scrub: use GFP_KERNEL on the submission pathfs/ | +13 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] GFP flags adjustments, part 2
Hi,
a few more tweaks to the GFP flags, for 4.5. This is low-risk and still preparatory so we can narrow down the contexts where we can utilize the more fine-grained GFP flags and attack the memory allocation failures.
----------------------------------------------------------------
The following changes since commit 39a27ec1004e886f1d949bdb8f2616896d02c5c2:
btrfs: use GFP_KERNEL for xattr and acl allocations (2015-12-03 15:03:44 +0100)
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 3677d94d23ae74d584ba61396aa51e82bb53e2d4:
btrfs: scrub: use GFP_KERNEL on the submission path (2016-01-19 10:17:31 +0100)
----------------------------------------------------------------
David Sterba (3):
btrfs: send: use GFP_KERNEL everywhere
btrfs: reada: use GFP_KERNEL everywhere
btrfs: scrub: use GFP_KERNEL on the submission path
fs/btrfs/reada.c | 10 +++++----- fs/btrfs/scrub.c | 24 +++++++++++++----------- fs/btrfs/send.c | 36 ++++++++++++++++++------------------ 3 files changed, 36 insertions(+), 34 deletions(-)
Signature · 1 line
2.6.3