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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 10 Jul 2014 15:15:51 -0700
From:	Andrew Morton <>
To:	Oded Gabbay <>
Cc:	David Airlie <>,
	Alex Deucher <>,
	Jerome Glisse <>,,,
	John Bridgman <>,
	Andrew Lewycky <>,
	Joerg Roedel <>, linux-mm <>,
	Oded Gabbay <>,
	Naoya Horiguchi <>,
	Joonsoo Kim <>,
	"Kirill A. Shutemov" <>,
	Hugh Dickins <>,
	Cyrill Gorcunov <>,
	Jérôme Glisse <>,
	Jianyu Zhan <>
Subject: Re: [PATCH 28/83] mm: Change timing of notification to IOMMUs about
 a page to be invalidated

On Fri, 11 Jul 2014 00:53:26 +0300 Oded Gabbay <> wrote:

> From: Andrew Lewycky <>
> This patch changes the location of the mmu_notifier_invalidate_page function
> call inside try_to_unmap_one. The mmu_notifier_invalidate_page function
> call tells the IOMMU that a pgae should be invalidated.
> The location is changed from after releasing the physical page to
> before releasing the physical page.
> This change should prevent the bug that would occur in the
> (rare) case where the GPU attempts to access a page while the CPU
> attempts to swap out that page (or discard it if it is not dirty).

um OK, but what is the effect on all the other
mmu_notifier_ops.invalidate_page() implementations?

Please spell this out in full detail within the changelog and be sure
to cc the affected maintainers.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists