diff options
| author | Dave Chinner <[email protected]> | 2024-01-16 09:59:40 +1100 |
|---|---|---|
| committer | Chandan Babu R <[email protected]> | 2024-02-13 18:07:34 +0530 |
| commit | f078d4ea827607867d42fb3b2ef907caf86ce49d (patch) | |
| tree | ae780ad789ce6c7668a4c9c3d16add40881fffd4 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 10634530f7ba947d8eab52a580e0840778d4ef75 (diff) | |
xfs: convert kmem_alloc() to kmalloc()
kmem_alloc() is just a thin wrapper around kmalloc() these days.
Convert everything to use kmalloc() so we can get rid of the
wrapper.
Note: the transaction region allocation in xlog_add_to_transaction()
can be a high order allocation. Converting it to use
kmalloc(__GFP_NOFAIL) results in warnings in the page allocation
code being triggered because the mm subsystem does not want us to
use __GFP_NOFAIL with high order allocations like we've been doing
with the kmem_alloc() wrapper for a couple of decades. Hence this
specific case gets converted to xlog_kvmalloc() rather than
kmalloc() to avoid this issue.
Signed-off-by: Dave Chinner <[email protected]>
Reviewed-by: "Darrick J. Wong" <[email protected]>
Signed-off-by: Chandan Babu R <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions