On Wed, Jul 31, 2024 at 8:59 AM Andrew Morton wrote:
>
> On Mon, 29 Jul 2024 10:37:08 +0800 Yafang Shao wrote:
>
> > Is it appropriate for you to apply this to the mm tree?
>
> There are a couple of minor conflicts against current 6.11-rc1 which
> you'd best check. So please redo this against cu
On Mon, 29 Jul 2024 10:37:08 +0800 Yafang Shao wrote:
> Is it appropriate for you to apply this to the mm tree?
There are a couple of minor conflicts against current 6.11-rc1 which
you'd best check. So please redo this against current mainline?
On Mon, Jul 29, 2024 at 5:29 PM Jani Nikula wrote:
>
> On Mon, 29 Jul 2024, Yafang Shao wrote:
> > Hello Andrew,
> >
> > Is it appropriate for you to apply this to the mm tree?
> >
> > Using {memcpy,strncpy,strcpy,kstrdup} to copy the task comm relies on the
> > length of task comm. Changes in th
On Mon, 29 Jul 2024, Yafang Shao wrote:
> Hello Andrew,
>
> Is it appropriate for you to apply this to the mm tree?
>
> Using {memcpy,strncpy,strcpy,kstrdup} to copy the task comm relies on the
> length of task comm. Changes in the task comm could result in a destination
> string that is overflow.
