From: Andrey Borzenkov <arvidjaar@mail.ru>
To: bridge@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] [2.6.15.4] Fix has_bridge_parent undefined with CONFIG_NETFILTER_DEBUG
Date: Sat, 11 Feb 2006 16:32:35 +0300 [thread overview]
Message-ID: <200602111632.36093.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Apparently introduced in the latest stable set; I am not sure if this is a
right fix but given that bridge parent already exists at this point it was
rather silly to fetch it again.
- -regards
- -andrey
Subject: [PATCH] [2.6.15.4] Fix has_bridge_parent undefined with
CONFIG_NETFILTER_DEBUG
This changes br_nf_post_routing to use realoutdev in debug print. At this
time it is equal to bridge_parent and is guaranteed to be not NULL.
Signed-off-by: Andrey Borzenkov <arvidjaar@mail.ru>
- ---
net/bridge/br_netfilter.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
db15f4ffe50096ba1585cfa344a440626724cfda
diff --git a/net/bridge/br_netfilter.c b/net/bridge/br_netfilter.c
index 0770664..37e085b 100644
- --- a/net/bridge/br_netfilter.c
+++ b/net/bridge/br_netfilter.c
@@ -793,9 +793,7 @@ static unsigned int br_nf_post_routing(u
#ifdef CONFIG_NETFILTER_DEBUG
print_error:
if (skb->dev != NULL) {
- - printk("[%s]", skb->dev->name);
- - if (has_bridge_parent(skb->dev))
- - printk("[%s]", bridge_parent(skb->dev)->name);
+ printk("[%s][%s]", skb->dev->name, realoutdev->name);
}
printk(" head:%p, raw:%p, data:%p\n", skb->head, skb->mac.raw,
skb->data);
- --
1.1.6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD7edzR6LMutpd94wRAngvAJsGuZqITozDySJ1UOHH2fs9zkoRMACfXT19
RvWlH+TGksJk+hDU9d2pR+o=
=yXVz
-----END PGP SIGNATURE-----
next reply other threads:[~2006-02-11 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 13:32 Andrey Borzenkov [this message]
2006-02-13 12:32 ` Luiz Fernando Capitulino
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=200602111632.36093.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=bridge@osdl.org \
--cc=linux-kernel@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
Powered by JetHome