From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [Bug 42809] New: kernel panic when receiving an ipsec packet
Date: Wed, 22 Feb 2012 18:41:34 +0100 [thread overview]
Message-ID: <4F4528CE.7080702@linuxsystems.it> (raw)
In-Reply-To: <20120222092056.5fca788b@nehalam.linuxnetplumber.net>
Thanks for CCing netdev, I was thinking about doing the same.
Il 22/02/2012 18:20, Stephen Hemminger ha scritto:
> That is a really old kernel now. Could you try with later kernel?
I can (a few minutes during night) but I really need a fix for 2.6.32.
This is a production server with dozens of Xen virtual machines and a
heavily patched kernel (xen dom0, layer 7, imq, esfq, advanced routing
etc). I did test a "vanilla" kernel last night (not really vanilla, but
a clean official debian kernel) and I had the same problem.
Thanks,
Niccolò
next prev parent reply other threads:[~2012-02-22 17:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42809-100@https.bugzilla.kernel.org/>
2012-02-22 17:20 ` [Bug 42809] New: kernel panic when receiving an ipsec packet Stephen Hemminger
2012-02-22 17:41 ` Niccolò Belli [this message]
2012-02-23 0:59 ` Niccolò Belli
2012-02-23 1:38 ` Eric Dumazet
2012-02-23 1:46 ` [openadsl-users] " Jason White
2012-02-23 1:54 ` Eric Dumazet
2012-02-23 13:48 ` Bug#660804: " chas williams - CONTRACTOR
2012-02-23 1:55 ` Niccolò Belli
2012-02-23 2:02 ` Niccolò Belli
2012-02-23 2:06 ` Eric Dumazet
2012-02-23 2:12 ` Niccolò Belli
2012-02-23 13:45 ` Niccolò Belli
2012-02-23 14:36 ` Eric Dumazet
2012-02-23 14:39 ` Eric Dumazet
2012-02-23 19:08 ` Niccolò Belli
2012-02-23 20:11 ` David Miller
2012-02-23 20:17 ` Eric Dumazet
2012-02-23 20:23 ` David Miller
2012-02-23 20:28 ` Eric Dumazet
2012-02-23 20:55 ` [PATCH V2] ipsec: be careful of non existing mac headers Eric Dumazet
2012-02-23 21:53 ` 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=4F4528CE.7080702@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.