diff options
| author | Gao Xiang <[email protected]> | 2019-10-31 09:23:15 +0000 |
|---|---|---|
| committer | Theodore Ts'o <[email protected]> | 2019-11-15 03:19:11 +0000 |
| commit | 5500221ea1b72c550b61f88fe3e8afbb08445989 (patch) | |
| tree | abff9db3e85a302c51438e7b1ff83c5054a3d229 /net/unix/af_unix.c | |
| parent | ext4: code cleanup for get_next_id (diff) | |
| download | kernel-5500221ea1b72c550b61f88fe3e8afbb08445989.tar.gz kernel-5500221ea1b72c550b61f88fe3e8afbb08445989.zip | |
ext4: bio_alloc with __GFP_DIRECT_RECLAIM never fails
Similar to [1] [2], bio_alloc with __GFP_DIRECT_RECLAIM flags
guarantees bio allocation under some given restrictions, as
stated in block/bio.c and fs/direct-io.c So here it's ok to
not check for NULL value from bio_alloc().
[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]
Cc: Theodore Ts'o <[email protected]>
Cc: Andreas Dilger <[email protected]>
Cc: Ritesh Harjani <[email protected]>
Reviewed-by: Chao Yu <[email protected]>
Signed-off-by: Gao Xiang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Theodore Ts'o <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions