From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Wed, 29 May 2019 21:02:43 +0000 Subject: Re: [PATCH 1/7] General notification queue with user mmap()'able ring buffer Message-Id: <16193.1559163763@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <20190528162603.GA24097@kroah.com> <155905930702.7587.7100265859075976147.stgit@warthog.procyon.org.uk> <155905931502.7587.11705449537368497489.stgit@warthog.procyon.org.uk> <4031.1559064620@warthog.procyon.org.uk> <20190528231218.GA28384@kroah.com> <31936.1559146000@warthog.procyon.org.uk> In-Reply-To: To: Jann Horn Cc: dhowells@redhat.com, Greg KH , Al Viro , raven@themaw.net, linux-fsdevel , Linux API , linux-block@vger.kernel.org, keyrings@vger.kernel.org, linux-security-module , kernel list , Kees Cook , Kernel Hardening Jann Horn wrote: > Does this mean that refcount_read() isn't sufficient for what you want > to do with tracing (because for some reason you actually need to know > the values atomically at the time of increment/decrement)? Correct. There's a gap and if an interrupt or something occurs, it's sufficiently big for the refcount trace to go weird. I've seen it in afs/rxrpc where the incoming network packets that are part of the rxrpc call flow disrupt the refcounts noted in trace lines. David