linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Dushistov <dushistov@mail.ru>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5]: ufs: missed brelse and wrong baseblk
Date: Tue, 20 Jun 2006 20:30:31 +0400	[thread overview]
Message-ID: <20060620163031.GA17675@rain.homenetwork> (raw)
In-Reply-To: <20060619182833.GJ27946@ftp.linux.org.uk>

On Mon, Jun 19, 2006 at 07:28:33PM +0100, Al Viro wrote:
> But now we have the buffer_heads on page 0 in the state inconsistent with
> the reality - basically, fs/buffer.c helpers will assume that they are
> _still_ in the second state (known to be in hole), while in the reality
> they should be either in the first or in the third one (mapped to known
> disk block or not known).
> 
> It's not a fundamental problem; 
And if we'll write after that to 0th page,
data with size <=page size, we can get garbage(not zeroes) 
on the rest of page.

Definitely, after block allocation, 
we should touch pages from inode cache,
which belongs to block except current page.

>however, it does mean that using these
> helpers means using library functions in situation they'd never been designed
> for.  IOW, you need very careful analysis of the assumptions made by
> the entire bunch and, quite possibly, need versions modified for UFS.
May be there is some incomprehension here,
this series and all other my patches in -mm related to UFS
is not introduced write support for UFS, they fixes
bugs similar to which you point out in black corners 
of the existing implementation.

Note: almost all such bugs related to 
touch blockdev's cache instead of inode's cache, and working
with blockdev's buffer cache without take into consideration
that it's also page cache).

-- 
/Evgeniy


      parent reply	other threads:[~2006-06-20 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17 10:14 [PATCH 1/5]: ufs: missed brelse and wrong baseblk Evgeniy Dushistov
2006-06-18 16:20 ` Al Viro
2006-06-18 17:50   ` Al Viro
2006-06-19  6:47     ` Evgeniy Dushistov
2006-06-19  7:32       ` Al Viro
2006-06-19 13:17         ` Evgeniy Dushistov
2006-06-19 18:28           ` Al Viro
2006-06-19 18:58             ` Evgeniy Dushistov
2006-06-19 19:13               ` Al Viro
2006-06-20 16:30                 ` Evgeniy Dushistov
2006-06-20 16:30             ` Evgeniy Dushistov [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=20060620163031.GA17675@rain.homenetwork \
    --to=dushistov@mail.ru \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).