From: Christoph Hellwig <hch@infradead.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH] Reiser4 bug fixes
Date: Sat, 19 Aug 2006 21:16:12 +0100 [thread overview]
Message-ID: <20060819201612.GB12853@infradead.org> (raw)
In-Reply-To: <44BE947F.30507@namesys.com>
On Wed, Jul 19, 2006 at 01:22:23PM -0700, Hans Reiser wrote:
> Hopefully this will make reiser4 stable code again. Or at least, a lot more stable than v3 (or other FSes) was when it went in....
>
>
> Signed-off-by: Hans Reiser
>
> From: Vladimir Saveliev <vs@namesys.com>
>
> This patch contains 4 reiser4 bug fixes:
> - missing long term lock unlock on read' error handling code path is added
> - truncate_inode_pages is now called with embedded mapping.
> It is needed to deal properly with block device special files.
> - copy_to_user might be called for more bytes than was prefaulted with fault_in_pages_writeable.
> That caused undesirable major page faults.
> - readdir bug similar to the previous one:
> call to filldir might lead to deadlock due to major page fault.
>
> Signed-off-by: Vladimir Saveliev <vs@namesys.com>
>
>
>
> diff -puN fs/reiser4/super_ops.c~reiser4-one-line-fixes fs/reiser4/super_ops.c
> --- linux-2.6.18-rc-mm2/fs/reiser4/super_ops.c~reiser4-one-line-fixes 2006-07-19 16:25:49.000000000 +0400
> +++ linux-2.6.18-rc-mm2-vs/fs/reiser4/super_ops.c 2006-07-19 16:25:49.000000000 +0400
> @@ -202,7 +202,7 @@ static void reiser4_delete_inode(struct
> fplug->delete_object(inode);
> }
>
> - truncate_inode_pages(inode->i_mapping, 0);
> + truncate_inode_pages(&inode->i_data, 0);
Where do you reset i_mapping to be different from i_data? It is a valid
thing to do in theory (that's why we have those different fields), but in
practice most usages I've seen are bogus.
(And yes, this is not a personal attack again you, just a normal review)
prev parent reply other threads:[~2006-08-19 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:22 Hans Reiser
2006-08-19 20:16 ` Christoph Hellwig [this message]
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=20060819201612.GB12853@infradead.org \
--to=hch@infradead.org \
--cc=Linux-Kernel@vger.kernel.org \
--cc=akpm@osdl.org \
--cc=reiser@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
all inboxes | Powered by JetHome®