[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250423095941.1cab813f@gandalf.local.home>
Date: Wed, 23 Apr 2025 09:59:41 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mykyta Yatsenko <mykyta.yatsenko5@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
mhiramat@...nel.org, andrii@...nel.org, kernel-team@...a.com,
linux-kernel@...r.kernel.org, Mykyta Yatsenko <yatsenko@...a.com>, Kees
Cook <keescook@...omium.org>
Subject: Re: [PATCH v2] maccess: fix strncpy_from_user_nofault empty string
handling
On Wed, 23 Apr 2025 12:37:46 +0100
Mykyta Yatsenko <mykyta.yatsenko5@...il.com> wrote:
> > Does this fix any known runtime issue? If so, please fully describe this?
> Not that I'm aware of. The issue could be found when trying to copy empty
> user space string in BPF program (and relying on return value).There are
> some usage of
> `strncpy_from_user_nofault` in tracing subsystem, but I'm not sure how to
> hit those code paths.
> >
Although your patch found a bug in the tracing subsystem, this wasn't the
cause. It only cared if the read faulted or not. It was incorrectly
checking for zero as non fault when in reality, it needed to check >= 0.
With that fixed, it should work the same with or without this patch.
-- Steve
Powered by blists - more mailing lists