Re: [PATCH] mm/mmu_notifier: Remove non_block_start/end() from notifier invocation
Jason Gunthorpe <[email protected]>
| Newsgroups | dev.linux.lists.linux-rt-devel,org.kernel.vger.kvm,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 12, 2026 at 09:21:31AM +0100, David Woodhouse wrote: > On Wed, 2026-08-12 at 10:14 +0200, Michal Hocko wrote: > > On Tue 11-08-26 16:24:48, David Woodhouse wrote: > > [...] > > > I had a second reason for disabling the overzealous check too: to allow > > > SRCU grace periods within the notifier callbacks. > > > > Is there a way that srcu barrier could cause an indirect dependency on > > memory allocation? In other words what might block the scru to complete? > > Not after https://lore.kernel.org/all/[email protected]/ The user of the SRCU might have a read side that wraps an allocate. In general it is not safe. I'm skeptical that without special API and documentation the KVM special use of SRCU you've outlined will not remain working long term too.. Jason