[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d533e64-8543-402d-9295-5fd2f314f35d@web.de>
Date: Sat, 4 Oct 2025 10:45:22 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Neil Brown <neil@...wn.name>, linux-cifs@...r.kernel.org
Cc: Neil Brown <neilb@...mail.net>, LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, Namjae Jeon <linkinjeon@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Stefan Metzmacher <metze@...ba.org>, Steve French <smfrench@...il.com>,
Tom Talpey <tom@...pey.com>
Subject: Re: ksmbd: Use common error handling code in ksmbd_vfs_path_lookup()
…> - declare struct path path __free(path_-put) = {};
…> return_path->dentry = no_free_ptr(path.dentry);
> return_path->mnt = no_free_ptr(path.mnt);
> return 0;
>
> This is based on the pattern in kern_path_parent() and
> __start_removing_path().
Do you propose that affected software components may benefit more from
the application of scope-based resource management?
https://elixir.bootlin.com/linux/v6.17/source/include/linux/path.h#L22-L28
Regards,
Markus
Powered by blists - more mailing lists