[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210323081353.GM62598@gauss3.secunet.de>
Date: Tue, 23 Mar 2021 09:13:53 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: "Ahmed S. Darwish" <a.darwish@...utronix.de>
CC: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Sebastian A. Siewior" <sebastian.siewior@...utronix.de>
Subject: Re: [PATCH v1 0/2] net: xfrm: Use seqcount_spinlock_t
On Tue, Mar 16, 2021 at 11:56:28AM +0100, Ahmed S. Darwish wrote:
> Hi,
>
> This is a small series to trasform xfrm_state_hash_generation sequence
> counter to seqcount_spinlock_t, instead of plain seqcount_t.
>
> In general, seqcount_LOCKNAME_t sequence counters allows to associate
> the lock used for write serialization with the seqcount. This enables
> lockdep to verify that the write serialization lock is always held
> before entering the seqcount write section.
>
> If lockdep is disabled, this lock association is compiled out and has
> neither storage size nor runtime overhead.
>
> The first patch is a general mainline fix, and has a Fixes tag.
>
> Thanks,
>
> 8<----------
>
> Ahmed S. Darwish (2):
> net: xfrm: Localize sequence counter per network namespace
> net: xfrm: Use sequence counter with associated spinlock
Applied to the ipsec tree, thanks a lot!
Powered by blists - more mailing lists