From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, airlied@linux.ie,
linux-kernel@vger.kernel.org, len.brown@intel.com, axboe@suse.de,
sfrench@us.ibm.com, rolandd@cisco.com, wim@iguana.be,
aia21@cantab.net, linux@dominikbrodowski.net
Subject: Re: git status (was: drm tree for 2.6.16-rc1)
Date: Thu, 12 Jan 2006 22:57:09 +0000 [thread overview]
Message-ID: <1137106630.3085.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20060112140713.770be59c.akpm@osdl.org>
On Thu, 2006-01-12 at 14:07 -0800, Andrew Morton wrote:
> Well it's oopsing in the audit code, and might not oops without audit.
> Perhaps the audit code is being called before i_sb is fully set up or
> something. We won't know until we know.
>
> Did we work out why i_sb is crazy?
No, we didn't. He disabled auditing (which he never really wanted in the
first place, but Fedora Core 4 stupidly enables it by default), then I
believe his last mail reported a BUG() in skb_under_panic(). It all
looks fairly random to me.
--
dwmw2
next prev parent reply other threads:[~2006-01-12 22:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 9:52 [git tree] drm tree for 2.6.16-rc1 Dave Airlie
2006-01-12 18:17 ` Linus Torvalds
2006-01-12 20:33 ` Dave Airlie
2006-01-12 21:52 ` Linus Torvalds
2006-01-12 21:42 ` git status (was: drm tree for 2.6.16-rc1) Andrew Morton
2006-01-12 21:55 ` Dominik Brodowski
2006-01-12 21:55 ` David Woodhouse
2006-01-12 22:07 ` Andrew Morton
2006-01-12 22:57 ` David Woodhouse [this message]
2006-01-12 22:07 ` git status Roland Dreier
2006-01-12 22:11 ` git status (was: drm tree for 2.6.16-rc1) Dmitry Torokhov
2006-01-15 9:55 ` Wim Van Sebroeck
2006-01-12 22:55 ` Stuff left for 2.6.16-rc1 (was: [git tree] " Russell King
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=1137106630.3085.11.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=aia21@cantab.net \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rolandd@cisco.com \
--cc=sfrench@us.ibm.com \
--cc=torvalds@osdl.org \
--cc=wim@iguana.be \
/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.