aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-memcpy.c
diff options
context:
space:
mode:
authorDmitry Kadashev <[email protected]>2021-07-08 13:34:38 +0700
committerJens Axboe <[email protected]>2021-08-23 13:41:26 -0600
commit0ee50b47532a81ab36046241822d1ecb4e08e76d (patch)
tree53566958c094a96c19e73806561d2b39d41a67a5 /lib/test_fortify/write_overflow-memcpy.c
parent91ef658fb8b82837f94ea0d45d14b5b2d2541e70 (diff)
namei: change filename_parentat() calling conventions
Since commit 5c31b6cedb675 ("namei: saner calling conventions for filename_parentat()") filename_parentat() had the following behavior WRT the passed in struct filename *: * On error the name is consumed (putname() is called on it); * On success the name is returned back as the return value; Now there is a need for filename_create() and filename_lookup() variants that do not consume the passed filename, and following the same "consume the name only on error" semantics is proven to be hard to reason about and result in confusing code. Hence this preparation change splits filename_parentat() into two: one that always consumes the name and another that never consumes the name. This will allow to implement two filename_create() variants in the same way, and is a consistent and hopefully easier to reason about approach. Link: https://lore.kernel.org/io-uring/CAOKbgA7MiqZAq3t-HDCpSGUFfco4hMA9ArAE-74fTpU+EkvKPw@mail.gmail.com/ Cc: Al Viro <[email protected]> Cc: Christian Brauner <[email protected]> Acked-by: Linus Torvalds <[email protected]> Signed-off-by: Dmitry Kadashev <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions