From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] [PATCH] corrupted reiserfs may cause kernel to panic on lookup() sometimes.
Date: Fri, 11 Jan 2002 12:46:26 -0500 [thread overview]
Message-ID: <147220000.1010771186@tiny> (raw)
In-Reply-To: <20020103101830.A2610@namesys.com>
In-Reply-To: <20020103101830.A2610@namesys.com>
On Thursday, January 03, 2002 10:18:30 AM +0300 Oleg Drokin
<green@namesys.com> wrote:
> Hello!
>
> Certain disk corruptions and i/o errors may cause lookup() to panic,
> which is wrong. This patch fixes the problem.
> Please apply.
Hmmm, none of the callers of reiserfs_find_entry have been changed to check
for IO_ERROR. We should at least change reiserfs_add_entry to check for
IO_ERROR, so it doesn't try to create a name after getting io error during
the lookup.
-chris
--- linux/fs/reiserfs/namei.c.orig Tue Dec 25 16:27:27 2001
+++ linux/fs/reiserfs/namei.c Tue Dec 25 16:29:13 2001
@@ -309,9 +309,10 @@
while (1) {
retval = search_by_entry_key (dir->i_sb, &key_to_search, path_to_entry, de);
- if (retval == IO_ERROR)
- // FIXME: still has to be dealt with
- reiserfs_panic (dir->i_sb, "zam-7001: io error in " __FUNCTION__ "\n");
+ if (retval == IO_ERROR) {
+ reiserfs_warning ("zam-7001: io error in " __FUNCTION__ "\n");
+ return IO_ERROR;
+ }
/* compare names for all entries having given hash value */
retval = linear_search_in_dir_item (&key_to_search, de, name, namelen);
next prev parent reply other threads:[~2002-01-11 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 7:18 [PATCH] corrupted reiserfs may cause kernel to panic on lookup() sometimes Oleg Drokin
2002-01-11 17:46 ` Chris Mason [this message]
2002-01-14 5:56 ` [reiserfs-dev] " Oleg Drokin
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=147220000.1010771186@tiny \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox