From: Borislav Petkov <bp@alien8.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Gao feng <gaofeng@cn.fujitsu.com>,
George Spelvin <linux@horizon.com>,
kaber@trash.net, linux-kernel@vger.kernel.org,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: v3.10-rc7 oops soon after boot
Date: Mon, 24 Jun 2013 18:13:05 +0200 [thread overview]
Message-ID: <20130624161305.GC26766@pd.tnic> (raw)
In-Reply-To: <20130624151031.GB3917@localhost>
On Mon, Jun 24, 2013 at 05:10:31PM +0200, Pablo Neira Ayuso wrote:
> > I have mangled your patch, find it attached.
>
> > From 79da8ea854c06ca9320decbb2f9d2e8d25b2f7e5 Mon Sep 17 00:00:00 2001
> > From: Gao feng <gaofeng@cn.fujitsu.com>
> > Date: Mon, 24 Jun 2013 17:04:02 +0800
> > Subject: [PATCH] netfilter: ipt_ULOG: fix incorrect setting of ulog timer
> >
> > The parameter of setup_timer should be &ulog->nlgroup[i].
> > the incorrect parameter will cause kernel panic in
> > ulog_timer.
> >
> > Bug introducted in commit 355430671ad93546b34b4e91bdf720f3a704efa4
> > "netfilter: ipt_ULOG: add net namespace support for ipt_ULOG"
> >
> > ebt_ULOG doesn't have this problem.
> >
> > Reported-by: Borislav Petkov <bp@alien8.de>
This should be:
Reported-by: George Spelvin <linux@horizon.com>
I only connected the dots...
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-06-24 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130624094145.2576.qmail@science.horizon.com>
[not found] ` <51C816C8.4080709@cn.fujitsu.com>
[not found] ` <20130624113441.GA2583@localhost>
2013-06-24 15:10 ` v3.10-rc7 oops soon after boot Pablo Neira Ayuso
2013-06-24 16:13 ` Borislav Petkov [this message]
2013-06-24 22:17 ` George Spelvin
2013-06-24 22:34 ` Borislav Petkov
2013-06-25 1:36 ` Gao feng
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=20130624161305.GC26766@pd.tnic \
--to=bp@alien8.de \
--cc=gaofeng@cn.fujitsu.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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).