From: Andrew Morton <akpm@osdl.org>
To: David Woodhouse <dwmw2@infradead.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 14:07:13 -0800 [thread overview]
Message-ID: <20060112140713.770be59c.akpm@osdl.org> (raw)
In-Reply-To: <1137102945.3621.1.camel@pmac.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Thu, 2006-01-12 at 13:42 -0800, Andrew Morton wrote:
> > audit: we're tracking one oops which seems to be coming out of the
> > audit code
>
> Are we? I recall one oops which was tracked down to an inode which had
> i_sb == 0x00000008 so it didn't seem to be audit-related. Was there
> something else I should be looking at?
>
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?
next prev parent reply other threads:[~2006-01-12 22:08 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 [this message]
2006-01-12 22:57 ` David Woodhouse
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=20060112140713.770be59c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cantab.net \
--cc=airlied@linux.ie \
--cc=axboe@suse.de \
--cc=dwmw2@infradead.org \
--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 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).