linux-kernel - Re: [PATCH/RFC] Add MM_DEAD flag to struct mm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1185518513.5495.184.camel@localhost.localdomain>
Date:	Fri, 27 Jul 2007 16:41:53 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	linux-mm <linux-mm@...ck.org>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH/RFC] Add MM_DEAD flag to struct mm_struct

On Fri, 2007-07-27 at 12:01 +1000, Benjamin Herrenschmidt wrote:
> Some architectures like sparc can do useful optimizations when knowing
> that an entire MM is being destroyed. At the moment, they rely on
> fullmm in the mmu_gather structure. However, that doesn't always work
> out very well with some of the changes we are doing. Among other things,
> the TLB flushing on sparc64 is done using per-CPU tracking data, making
> the batch not per-CPU will break that link.
> 
> So instead, we add a new flag to struct mm_struct that indicates that
> the mm is going away, for those archs to use. It also allows to use it
> in situations (such as PTE ops) where the batch isn't accessible (or
> there is no batch)

And the patch forgets to clear it in mm_init ... will send a new one
later.

Cheers,
Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/