From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: conntrack: don't acquire lock during seq_printf
Date: Thu, 14 Apr 2016 12:05:42 +0200 [thread overview]
Message-ID: <20160414100542.GA2644@salvia> (raw)
In-Reply-To: <20160414094346.GA2056@salvia>
On Mon, Apr 11, 2016 at 09:14:29PM +0200, Florian Westphal wrote:
> read access doesn't need any lock here.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> net/netfilter/nf_conntrack_proto_sctp.c | 8 +-------
> net/netfilter/nf_conntrack_proto_tcp.c | 8 +-------
> 2 files changed, 2 insertions(+), 14 deletions(-)
>
> diff --git a/net/netfilter/nf_conntrack_proto_sctp.c b/net/netfilter/nf_conntrack_proto_sctp.c
> index 9578a7c..1d7ab96 100644
> --- a/net/netfilter/nf_conntrack_proto_sctp.c
> +++ b/net/netfilter/nf_conntrack_proto_sctp.c
> @@ -191,13 +191,7 @@ static void sctp_print_tuple(struct seq_file *s,
> /* Print out the private part of the conntrack. */
> static void sctp_print_conntrack(struct seq_file *s, struct nf_conn *ct)
> {
> - enum sctp_conntrack state;
> -
> - spin_lock_bh(&ct->lock);
> - state = ct->proto.sctp.state;
Don't we need at least READ_ONCE() here?
> - spin_unlock_bh(&ct->lock);
> -
> - seq_printf(s, "%s ", sctp_conntrack_names[state]);
> + seq_printf(s, "%s ", sctp_conntrack_names[ct->proto.sctp.state]);
> }
>
> #define for_each_sctp_chunk(skb, sch, _sch, offset, dataoff, count) \
next prev parent reply other threads:[~2016-04-14 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 19:14 [PATCH nf-next] netfilter: conntrack: don't acquire lock during seq_printf Florian Westphal
[not found] ` <20160414094346.GA2056@salvia>
2016-04-14 10:05 ` Pablo Neira Ayuso [this message]
2016-04-14 11:16 ` Florian Westphal
2016-04-14 12:27 ` Pablo Neira Ayuso
2016-04-14 12:39 ` Florian Westphal
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=20160414100542.GA2644@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
/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).