From: Andrew Morton <akpm@zip.com.au>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Assertion failure / do_get_write_acess() / loop / samba
Date: Mon, 28 Jan 2002 10:41:02 -0800 [thread overview]
Message-ID: <3C559B3E.56D8BC2F@zip.com.au> (raw)
In-Reply-To: <008f01c1a815$d8cdcc70$8a140237@rennes.si.fr.atosorigin.com>
"Yann E. MORIN" wrote:
>
> Hi all!
>
> I've encountered a reproductible 'Assertion failure' in 2.4.17.
> It happens on pure vanilla, as well as on sched O1-J0, and also on
> 2.4.18-pre4.
>
Thanks. Could you please apply the ext3 debug patch at
http://www.zip.com.au/~akpm/linux/ext3/ext3-debug-2.4.18-pre6.patch
and enable `buffer head tracing' in config (filesystems menu)
and then send the crash result to ext2-devel@lists.sourceforge.net
-
next prev parent reply other threads:[~2002-01-28 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 16:07 Assertion failure / do_get_write_acess() / loop / samba Yann E. MORIN
2002-01-28 18:41 ` Andrew Morton [this message]
2002-01-29 11:42 ` Stephen C. Tweedie
2002-01-29 13:58 ` Yann E. MORIN
2002-01-29 14:24 ` Stephen C. Tweedie
2002-01-29 15:40 ` Yann E. MORIN
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=3C559B3E.56D8BC2F@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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