[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b6476b5d-5938-45e8-9c3b-14448a5d854f@gmail.com>
Date: Mon, 13 Nov 2023 01:48:14 +0530
From: Abhinav Singh <singhabhinav9051571833@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: akpm@...ux-foundation.org, brauner@...nel.org, surenb@...gle.com,
mst@...hat.com, michael.christie@...cle.com, mjguzik@...il.com,
mathieu.desnoyers@...icios.com, npiggin@...il.com,
linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH v4] Fixing directly deferencing a __rcu pointer warning
On 11/13/23 01:28, Peter Zijlstra wrote:
> On Mon, Nov 13, 2023 at 01:00:55AM +0530, Abhinav Singh wrote:
>> This patch fixes the sparse warning with this message
>> "dereference of noderef expression" , in this context
>> it means about directly dereferencing a pointer tagged
>> with __rcu annotation.
>
> Please, stop this madness. Just accept that sparse is a stupid tool and
> the code is actually fine.
Thank you for your tine maintainers. Okay I understood that this extra
patch, is not required. Just one follow up question, in some driver code
as well I see these warning, might be possible those are real issue.
Can you suggest me like how do I know if a rcu related warning is really
a issue or just a false positive warning.
Thanks,
Abhinav.
Powered by blists - more mailing lists