Skip to content

Cleanup code that think bio_alloc with __GFP_WAIT can fail

Nikanth Karthikesan lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 of 7 patches 1 replyIn review

6 of 7 patches are in this archive. The cover letter announces 7.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/7Document that bio_alloc with __GFP_WAIT cannot failfs/bio.c+4 -00 replies
2/7block: Remove code handling bio_alloc failure with __GFP_WAITblock/blk-barrier.c block/ioctl.c+0 -50 replies
3/7dio: Remove code handling bio_alloc failure with __GFP_WAITfs/direct-io.c+0 -20 replies
4/7ext4: Remove code handling bio_alloc failure with __GFP_WAITfs/ext4/extents.c+0 -20 replies
6/7xfs: Remove code handling bio_alloc failure with __GFP_WAITfs/xfs/linux-2.6/xfs_aops.c+1 -40 replies
7/7swap: Remove code handling bio_alloc failure with __GFP_WAITkernel/power/swap.c+0 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/7] Cleanup code that think bio_alloc with __GFP_WAIT can fail

bio_alloc will not fail when __GFP_WAIT is specified in the gfp_flags. See
http://lkml.org/lkml/2009/4/14/198 for the discussion. But this not documented and there are places where there is unwanted code to handle bio_alloc failure even when __GFP_WAIT is specified. This patch set documents this and cleans up various callers who assume bio_alloc can fail even with __GFP_WAIT.

Thanks
Nikanth