From: Steffen Klassert <steffen.klassert@secunet.com>
To: "Ahmed S. Darwish" <a.darwish@linutronix.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Sebastian A. Siewior" <sebastian.siewior@linutronix.de>
Subject: Re: [PATCH v1 0/2] net: xfrm: Use seqcount_spinlock_t
Date: Tue, 23 Mar 2021 09:13:53 +0100 [thread overview]
Message-ID: <20210323081353.GM62598@gauss3.secunet.de> (raw)
In-Reply-To: <20210316105630.1020270-1-a.darwish@linutronix.de>
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!
prev parent reply other threads:[~2021-03-23 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 10:56 [PATCH v1 0/2] net: xfrm: Use seqcount_spinlock_t Ahmed S. Darwish
2021-03-16 10:56 ` [PATCH v1 1/2] net: xfrm: Localize sequence counter per network namespace Ahmed S. Darwish
2021-03-16 10:56 ` [PATCH v1 2/2] net: xfrm: Use sequence counter with associated spinlock Ahmed S. Darwish
2021-03-23 8:13 ` Steffen Klassert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210323081353.GM62598@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=a.darwish@linutronix.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sebastian.siewior@linutronix.de \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).