From: David Miller <davem@davemloft.net>
To: rostedt@goodmis.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dada1@cosmosbay.com, mingo@elte.hu, akpm@linux-foundation.org,
acme@ghostprotocols.net
Subject: Re: [PATCH] update rwlock initialization for nat_table
Date: Mon, 15 Dec 2008 00:20:19 -0800 (PST) [thread overview]
Message-ID: <20081215.002019.232912990.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0812101504280.11805@gandalf.stny.rr.com>
From: Steven Rostedt <rostedt@goodmis.org>
Date: Wed, 10 Dec 2008 15:06:00 -0500 (EST)
> update rwlock initialization for nat_table
>
> Impact: clean up
>
> The commit e099a173573ce1ba171092aee7bb3c72ea686e59
> (netfilter: netns nat: per-netns NAT table) renamed the
> nat_table from __nat_table to nat_table without updating the
> __RW_LOCK_UNLOCKED(__nat_table.lock).
>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Applied to net-2.6, thanks Steven.
As Andrew mentioned this is a bug (albeit a "nano-bug" as you
called it :-) so I removed the Impact line in the commit
message when applying this.
Thanks!
next prev parent reply other threads:[~2008-12-15 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 18:21 [PATCH] replace deprecated RW_LOCK_UNLOCKED in net/dccp/proto.c Steven Rostedt
2008-12-10 18:33 ` Eric Dumazet
2008-12-10 19:00 ` Steven Rostedt
2008-12-10 20:06 ` [PATCH] update rwlock initialization for nat_table Steven Rostedt
2008-12-11 22:18 ` Andrew Morton
2008-12-11 22:24 ` Steven Rostedt
2008-12-15 8:20 ` David Miller [this message]
2008-12-16 1:10 ` Impact: (was Re: [PATCH] update rwlock initialization for nat_table) Alexey Dobriyan
2008-12-16 1:19 ` Andrew Morton
2008-12-16 11:15 ` Arnaldo Carvalho de Melo
2008-12-16 6:38 ` Impact: David Miller
2008-12-16 23:00 ` Impact: (was Re: [PATCH] update rwlock initialization for nat_table) Ingo Molnar
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=20081215.002019.232912990.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®