Re: [PATCH 10/13] mm/migrate_device: refuse to migrate shadow stacks

[Roman Gushchin <roman.gushchin@linux.dev>]

"Lorenzo Stoakes (ARM)" <ljs@kernel.org> writes:

> On Thu, Nov 12, 2026 at 02:53:44PM -0800, Roman Gushchin wrote:
>> > On Nov 12, 2026, at 11:03 AM, Lorenzo Stoakes (ARM) <ljs@kernel.org> wrote:
>> >
>> > +cc Roman
>> >
>> > Roman - see below - I was under the impression mm was not supposed to receive
>> > 'unrelated to this patch but' reports? Did something change?
>>
>> Yes, sashiko started reporting pre-existing bugs again, but in a better way:
>> strictly once (per bug)
>> only for the first non-rfc version
>> somewhat related to the proposed patch
>> not more than 1-2 per patch
>> not exposing security-sensitive stuff this way
>>
>> Obviously the goal here it to increase the chances for the problem to be fixed.
>> It’s global, not mm-specific.
>
> (Sorry only just saw this!)
>
> Ah, I thought it was an mm opt-out.
>
> In general they're spawning a lot of AI sloppers to go off and send ever
> more fixes and causing ever longer days for us, it's quite a noticeable
> impact unfortunately.
>
> And often they're duplicative of already-sent fixes so you can see the
> conundrum with this :)
>
> So ideally we'd like a way to embargo these or have a maintainers-only view
> of them etc. so we can figure out a way of reasonably getting to valid
> cases.

Disabled for mm. Maintainers-only view is available in the database.

Thanks