From: Chris Mason <mason@suse.com>
To: Pavel Machek <pavel@suse.cz>,
viro@math.psu.edu, kernel list <linux-kernel@vger.kernel.org>,
jack@atrey.karlin.mff.cuni.cz
Cc: torvalds@transmeta.com
Subject: Re: [patch] linux likes to kill bad inodes
Date: Fri, 27 Apr 2001 10:36:44 -0400 [thread overview]
Message-ID: <221900000.988382204@tiny> (raw)
In-Reply-To: <20010427002853.A11426@bug.ucw.cz>
On Friday, April 27, 2001 12:28:54 AM +0200 Pavel Machek <pavel@suse.cz>
wrote:
> Okay, so what about following patch, followed by attempt to debug it?
> [I'd really like to get patch it; killing user's data without good
> reason seems evil to me, and this did quite a lot of damage to my
> $HOME.]
2.4.4-pre8 does have the patch to keep write_inode from syncing a
bad_inode. In the short term this is the best way to go.
For debugging further, it is probably best to put the warning in when
marking the inode dirty, and randomly returning bad_inodes from read_inode.
I'll give this a try next week.
My guess is that UPDATE_ATIME is the offending caller, the follow_link path
in open_namei is at least one place that should trigger it.
-chris
next prev parent reply other threads:[~2001-04-27 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 12:10 [patch] linux likes to kill bad inodes Pavel Machek
2001-04-25 13:29 ` Chris Mason
2001-04-25 20:01 ` Pavel Machek
2001-04-25 20:28 ` Chris Mason
2001-04-26 9:28 ` Pavel Machek
2001-04-26 9:33 ` Jan Kara
2001-04-26 22:28 ` Pavel Machek
2001-04-27 14:36 ` Chris Mason [this message]
2001-04-27 22:07 ` Andreas Dilger
2001-04-27 22:14 ` Linus Torvalds
2001-04-30 22:28 ` Alan Cox
2001-04-30 22:33 ` David S. Miller
2001-04-30 23:22 ` Linus Torvalds
[not found] <no.id>
2001-04-27 23:30 ` Andreas Dilger
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=221900000.988382204@tiny \
--to=mason@suse.com \
--cc=jack@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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