From: Vlad Apostolov <vapo@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs vs. lockdep
Date: Tue, 10 Oct 2006 13:23:38 +1000 [thread overview]
Message-ID: <452B123A.9030700@sgi.com> (raw)
In-Reply-To: <452B0E53.2070507@sandeen.net>
Eric Sandeen wrote:
> Vlad Apostolov wrote:
>
>> Hi Eric,
>>
>> Could you please provide some more information. What kernel, test
>> case and call stack at the time of the crash.
>>
>> Thanks,
>> Vlad
>
> Vlad, for reference, this was a very recent FC6 test kernel, which has
> lockdep & slab debugging on. Oopsing is as simple as mounting &
> umounting. It dies in lockdep code.
>
> See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209062
>
> -Eric
>
Thanks Eric,
I opened a pv and I see David C. replied to your email too.
Vlad
next prev parent reply other threads:[~2006-10-10 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 17:58 xfs vs. lockdep Eric Sandeen
2006-10-09 23:36 ` Vlad Apostolov
2006-10-10 3:06 ` Eric Sandeen
2006-10-10 3:23 ` Vlad Apostolov [this message]
2006-10-10 0:47 ` David Chinner
2006-10-10 1:45 ` Timothy Shimmin
2006-10-10 2:21 ` Eric Sandeen
2006-10-10 4:55 ` Timothy Shimmin
2006-10-10 2:25 ` Eric Sandeen
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=452B123A.9030700@sgi.com \
--to=vapo@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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