[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjZfO9hGqJ2_hGQG3U_XzSh9_XaXze=HgPdvJbgrvASfA@mail.gmail.com>
Date: Thu, 30 Jun 2022 09:34:10 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alexander Aring <aahringo@...hat.com>
Cc: Will Deacon <will@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Boqun Feng <boqun.feng@...il.com>,
Mark Rutland <mark.rutland@....com>,
thunder.leizhen@...wei.com, jacob.e.keller@...el.com,
Andrew Morton <akpm@...ux-foundation.org>,
Sparse Mailing-list <linux-sparse@...r.kernel.org>,
cluster-devel <cluster-devel@...hat.com>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 0/2] refcount: attempt to avoid imbalance warnings
On Thu, Jun 30, 2022 at 6:59 AM Alexander Aring <aahringo@...hat.com> wrote:
>
> I send this patch series as RFC because it was necessary to do a kref
> change after adding __cond_lock() to refcount_dec_and_lock()
> functionality.
Can you try something like this instead?
This is two separate patches - one for sparse, and one for the kernel.
This is only *very* lightly tested (ie I tested it on a single kernel
file that used refcount_dec_and_lock())
Linus
View attachment "sparse.patch" of type "text/x-patch" (2345 bytes)
View attachment "kernel.patch" of type "text/x-patch" (2002 bytes)
Powered by blists - more mailing lists