[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026010816-unsolved-wipe-bc45@gregkh>
Date: Thu, 8 Jan 2026 08:55:49 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Usyskin, Alexander" <alexander.usyskin@...el.com>
Cc: "Abliyev, Reuven" <reuven.abliyev@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [char-misc v2] mei: trace: treat reg parameter as string
On Thu, Jan 08, 2026 at 07:42:22AM +0000, Usyskin, Alexander wrote:
> > Subject: Re: [char-misc v2] mei: trace: treat reg parameter as string
> >
> > On Thu, Jan 08, 2026 at 08:57:02AM +0200, Alexander Usyskin wrote:
> > > Use the string wrapper to check sanity of the reg parameters,
> > > store it value independently and prevent internal kernel data leaks.
> > > Trace subsystem refuses to emit event with plain char*,
> > > without the wrapper.
> > >
> > > Cc: stable@...r.kernel.org
> >
> > Does this really fix a bug? If not, there's no need for cc: stable or:
> >
> > > Fixes: a0a927d06d79 ("mei: me: add io register tracing")
> >
> > That line as well.
> >
> > thanks,
> >
> > greg k-h
>
> Without this patch the events are not emitted at all, they are dropped
> by trace security checker.
Ah, again, that was not obvious at all from the changelog. Perhaps
reword it a bit? How has this ever worked?
thanks,
greg k-h
Powered by blists - more mailing lists