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: Mon, 19 Jun 2006 22:58:16 +0400	[thread overview]
Message-ID: <20060619185816.GA26513@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:
> On Mon, Jun 19, 2006 at 05:17:50PM +0400, Evgeniy Dushistov wrote:
> > In case of 1k fragments, msync of two pages
> > cause 8 calls of ufs's get_block_t with create == 1,
> > they will be consequent because of synchronization.
> 
> _What_ synchronization?
> Now, which lock would, in your opinion, provide serialization between these
> two calls?  They apply to different pages, so page locks do not help.
>  
you can look at fs/ufs/inode.c: ufs_getfrag_block.
It is ufs's get_block_t,
if create == 1 it uses "[un]lock_kernel". 

> To simplify the analysis, have one of those do msync() and another - write().
> One triggers writeback, leading to ufs_writepage().  Another leads to call
> of ufs_prepare_write().  Note that the latter call is process-synchronous,
> so no implicit serialization could apply.
skiped

I'll think about this.

-- 
/Evgeniy


  reply	other threads:[~2006-06-19 18:52 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 [this message]
2006-06-19 19:13               ` Al Viro
2006-06-20 16:30                 ` Evgeniy Dushistov
2006-06-20 16:30             ` Evgeniy Dushistov

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=20060619185816.GA26513@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).