[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGudoHEfjSAim6Hh-qYPY+qi8nbLx7J3YdpGgFwSvD7xbeYR3w@mail.gmail.com>
Date: Thu, 26 Oct 2023 17:07:52 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Abhinav Singh <singhabhinav9051571833@...il.com>,
akpm@...ux-foundation.org, brauner@...nel.org, surenb@...gle.com,
michael.christie@...cle.com, npiggin@...il.com,
shakeelb@...gle.com, peterz@...radead.org,
linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH v2] Fixing directly deferencing a __rcu pointer warning
On 10/26/23, Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:
> Drive-by comment: perhaps use rcu_dereference_protected() ?
>
Definitely.
But as I mentioned even after applying the patch there are uses which
should have been reported (and consequently sorted out). If one is to
bother with any of this at least the entire file should be covered.
--
Mateusz Guzik <mjguzik gmail.com>
Powered by blists - more mailing lists