From: Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
To: Eric Dumazet <dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
Cc: Mariusz Kozlowski
<m.kozlowski-NWF1p15JEu3VItvQsEIGlw@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Netfilter Development Mailinglist
<netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Netdev List
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: panic on rmmod of nf_conntrack_irc
Date: Wed, 15 Apr 2009 12:26:53 +0200 [thread overview]
Message-ID: <49E5B66D.30602@trash.net> (raw)
In-Reply-To: <49E47C2D.1050508-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
Eric Dumazet wrote:
> I should have used different fields names (from "next", "first", ...) to catch this
> kind of errors at compile time :(
>
> Something like :
>
> diff --git a/include/linux/list_nulls.h b/include/linux/list_nulls.h
Eric, on second thought, could you please resubmit this to Dave?
It touches too many files outside of netfilter to go through my
tree.
next prev parent reply other threads:[~2009-04-15 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090410191736.21efab8c@mako-desktop>
2009-04-14 11:32 ` panic on rmmod of nf_conntrack_irc Patrick McHardy
2009-04-14 12:06 ` Eric Dumazet
2009-04-14 12:16 ` Patrick McHardy
2009-04-14 19:19 ` Mariusz Kozlowski
2009-04-14 20:06 ` Mariusz Kozlowski
2009-04-14 20:14 ` Eric Dumazet
2009-04-14 20:39 ` Mariusz Kozlowski
2009-04-14 20:46 ` Eric Leblond
2009-04-14 21:07 ` [PATCH] netfilter: nf_log fix Eric Dumazet
2009-04-15 10:20 ` Patrick McHardy
[not found] ` <49E47C2D.1050508-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org>
2009-04-15 10:26 ` Patrick McHardy [this message]
2009-04-15 10:42 ` panic on rmmod of nf_conntrack_irc Eric Dumazet
2009-04-15 10:44 ` Patrick McHardy
2009-04-15 10:45 ` David Miller
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=49E5B66D.30602@trash.net \
--to=kaber-dcujhnylwpneowh0uzbu5w@public.gmane.org \
--cc=dada1-fPLkHRcR87vqlBn2x/YWAg@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m.kozlowski-NWF1p15JEu3VItvQsEIGlw@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).