[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025-08-07.1754534735-core-snowplow-plaid-exiles-anemic-gulls-v9Da77@cyphar.com>
Date: Thu, 7 Aug 2025 12:46:17 +1000
From: Aleksa Sarai <cyphar@...har.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
David Howells <dhowells@...hat.com>, Shuah Khan <shuah@...nel.org>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v3 1/2] fscontext: do not consume log entries when
returning -EMSGSIZE
On 2025-08-06, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Thu, Aug 07, 2025 at 03:55:23AM +1000, Aleksa Sarai wrote:
>
> > - goto err_free;
> > - ret = -EFAULT;
> > - if (copy_to_user(_buf, p, n) != 0)
> > - goto err_free;
> > + if (copy_to_user(_buf, p, n))
> > + n = -EFAULT;
> > ret = n;
> > -
> > -err_free:
> > if (need_free)
> > kfree(p);
> > return ret;
>
> Minor nit: seeing that there's only one path to that return, I would
> rather turn it into
> return n;
> and dropped the assignment to ret a few lines above. Anyway, that's
> trivially done when applying...
It felt odd to use "return ret;" at the start and switch to "return n;"
at the end, but feel free to change it when applying.
> Anyway, who's carrying fscontext-related stuff this cycle? I've got
> a short series in that area, but there won't be much from me around
> there - a plenty of tree-in-dcache stuff, quite a bit of mount-related
> work, etc., but not a lot around the options-parsing machinery.
>
> Christian, do you have any plans around that area?
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
https://www.cyphar.com/
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists