All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org,
	Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: BUG: 2.6.25-rc1: iptables postrouting setup causes oops
Date: Thu, 14 Feb 2008 09:41:26 +1100	[thread overview]
Message-ID: <1202942486.3299.69.camel@moss.renham> (raw)
In-Reply-To: <20080213004829.fd8afdc7.akpm@linux-foundation.org>


On Wed, 2008-02-13 at 00:48 -0800, Andrew Morton wrote:
> On Tue, 12 Feb 2008 22:46:01 +1100 Ben Nizette <bn@niasdigital.com> wrote:

> > Perfectly repeatable.
> 
> If my theory is correct, changing pretty much anything in the kernel config
> might just make it go away.  But still, it would be most valuable if you
> could try running a bisection search, as described in
> http://www.kernel.org/doc/local/git-quick.html, thanks.
> 

Hm, not as stable a bug as I'd thought.  I have performed a number of
bisections with different start points and they have not converged on
the same patch twice.  Even bisections with the _same_ start point
didn't always converge on the same patch.

What ever the problem is it isn't immediately apparent in latest git so
I guess we'll just have to keep our eyes peeled.

Thanks,
	--Ben.

      parent reply	other threads:[~2008-02-13 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 11:46 BUG: 2.6.25-rc1: iptables postrouting setup causes oops Ben Nizette
2008-02-13  8:48 ` Andrew Morton
2008-02-13  9:10   ` Haavard Skinnemoen
2008-02-13  9:22     ` Andrew Morton
2008-02-13 16:42       ` Andrew G. Morgan
2008-02-13 18:19         ` Haavard Skinnemoen
2008-02-13 11:29     ` Haavard Skinnemoen
2008-02-13 22:41   ` Ben Nizette [this message]

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=1202942486.3299.69.camel@moss.renham \
    --to=bn@niasdigital.com \
    --cc=akpm@linux-foundation.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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 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.