From: Theodore Ts'o <tytso@mit.edu>
To: Peter Moody <pmoody@google.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Oops with ext(3|4) and audit and Xen
Date: Mon, 8 Oct 2012 17:15:00 -0400 [thread overview]
Message-ID: <20121008211500.GD22980@thunk.org> (raw)
In-Reply-To: <CALnj_=5eQ5vCmv8x3u-rJPzofqJr+WDJuYzkpZo8sLe0+B2AAw@mail.gmail.com>
On Mon, Oct 08, 2012 at 11:19:53AM -0700, Peter Moody wrote:
>
> I'm trying to track down a BUG() that seems to strike a particular
> system configuration (unfortunately, an increasingly common
> configuration), but does so with 100% reliability.
Peter, this looks like exactly the same issue that you asked me about
back in July, isn't it? Check your corp e-mail archives for the
subject line: "advice/pointers on debugging a potential kernel race".
As I recall, the problem was a missing path_put() in audit_putname()
in kernel/auditsc.c?
- Ted
next prev parent reply other threads:[~2012-10-08 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 18:19 Oops with ext(3|4) and audit and Xen Peter Moody
2012-10-08 19:08 ` Eric Sandeen
2012-10-08 21:03 ` Peter Moody
2012-10-08 21:41 ` Eric Sandeen
2012-10-08 21:39 ` Theodore Ts'o
2012-10-08 21:40 ` Eric Sandeen
2012-10-08 21:45 ` Peter Moody
2012-10-08 21:15 ` Theodore Ts'o [this message]
2012-10-08 21:19 ` Peter Moody
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=20121008211500.GD22980@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=pmoody@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox