Re: [PATCH v5 2/8] alpha: run check_mmu_context() from finish_arch_post_lock_switch()

From: Magnus Lindholm

Date: Sun Oct 11 2026 - 12:56:23 EST


Hi Matt,

On Sun, Oct 11, 2026 at 1:32 AM Matt Turner <mattst88@xxxxxxxxx> wrote:
>
> On Sat, Oct 10, 2026 at 04:24:28PM +0200, Magnus Lindholm wrote:
> > code following alpha_switch_to(). New kernel threads take the same
> > path through schedule_tail().
> >
> > asn_lock is left set on that CPU, so the new task can run with
>
> I missed this in v4. New kernel threads do take that path, but
> context_switch() does not call switch_mm() for a task without an mm, so
> they never set asn_lock in the first place. Only a new user task leaves
> it set. As written, the two paragraphs read as if both do.
>
> Changelog only, and not worth a v6. My Reviewed-by stands.

Thanks, fixed the changelog in for-next to make clear that only new user
tasks leave asn_lock set. New kernel threads reach schedule_tail(), but
skip switch_mm() and therefore do not set asn_lock.

No code changes; your Reviewed-by is retained.

Thanks,
Magnus