From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Zygo Blaxell <eazgwmir@umail.furryterror.org>, reiserfs-list@namesys.com
Subject: Re: How to break a reiserfs on Linux 2.4.20
Date: Thu, 16 Jan 2003 18:32:24 +0300 [thread overview]
Message-ID: <20030116183224.A32008@namesys.com> (raw)
In-Reply-To: <1042730943.31095.2188.camel@tiny.suse.com>
Hello!
On Thu, Jan 16, 2003 at 10:29:03AM -0500, Chris Mason wrote:
> These aren't good at all, either the locking on the commit lists is
> broken or the buffer head management is going wrong.
> Oleg, do you have any leads or do you want me to try reproducing?
Well, I found something looking like a race in VFS (I sent a mail to lkml
earlier today). reiserfs_link is called with inodes that have zero i_nlink.
But I do not see how that might explain journaling stuff.
I have not tried the script on SMP yet, though.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-16 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 19:30 2.4.20, reiserfs, md linear, and "Permission denied" Zygo Blaxell
2003-01-14 0:37 ` Zygo Blaxell
2003-01-14 16:56 ` How to break a reiserfs on Linux 2.4.20 Zygo Blaxell
2003-01-14 17:05 ` Nikita Danilov
2003-01-14 19:04 ` Zygo Blaxell
2003-01-14 19:15 ` Nikita Danilov
2003-01-14 22:39 ` Zygo Blaxell
2003-01-15 22:44 ` Zygo Blaxell
2003-01-16 7:49 ` Oleg Drokin
2003-01-16 14:16 ` Zygo Blaxell
2003-01-16 15:22 ` Oleg Drokin
2003-01-16 15:29 ` Chris Mason
2003-01-16 15:32 ` Oleg Drokin [this message]
2003-01-17 20:13 ` Zygo Blaxell
2003-01-14 17:53 ` Oleg Drokin
2003-01-14 19:02 ` Zygo Blaxell
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=20030116183224.A32008@namesys.com \
--to=green@namesys.com \
--cc=eazgwmir@umail.furryterror.org \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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 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.