[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14125758.fD4hS3u3Vl@sven-edge>
Date: Sun, 16 Feb 2020 17:17:36 +0100
From: Sven Eckelmann <sven@...fation.org>
To: Madhuparna Bhowmik <madhuparnabhowmik10@...il.com>
Cc: mareklindner@...mailbox.ch, sw@...onwunderlich.de, a@...table.cc,
davem@...emloft.net, b.a.t.m.a.n@...ts.open-mesh.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
joel@...lfernandes.org, frextrite@...il.com,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH] net: batman-adv: Use built-in RCU list checking
On Sunday, 16 February 2020 16:52:44 CET Madhuparna Bhowmik wrote:
[...]
> > I understand this part. I was asking how you've identified them. Did you use
> > any tool for that? coccinelle, sparse, ...
>
> Not really, I did it manually by inspecting each occurence.
In that case, I don't understand why you didn't convert the occurrences from
hlist_for_each_entry_rcu to hlist_for_each_entry [1]. Because a manual
inspection should have noticed that there will always be the lock around
these ones.
KInd regards,
Sven
[1] https://www.kernel.org/doc/html/v5.6-rc1/RCU/whatisRCU.html#analogy-with-reader-writer-locking
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists