All of lore.kernel.org
 help / color / mirror / Atom feed
From: hooanon05@yahoo.co.jp
To: Hugh Dickins <hugh@veritas.com>
Cc: Erez Zadok <ezk@cs.sunysb.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	mhalcrow@us.ibm.com, hch@infradead.org, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsstack: fsstack_copy_inode_size locking
Date: Mon, 30 Jun 2008 13:31:57 +0900	[thread overview]
Message-ID: <8725.1214800317@jrobl> (raw)
In-Reply-To: <Pine.LNX.4.64.0806290101160.20280@blonde.site>


Hugh Dickins:
> LTP's iogen01 doio tests used to hang nicely on 32-bit SMP when /tmp was a
> unionfs mount of a tmpfs, i_size_read spinning forever, waiting for a lost
> seqcount update: fixed by taking i_lock around i_size_write when 32-bit SMP.

I don't know why dst->i_lock is affected by src->i_size_seqcount.
Do you mean that your test issued write(2) to the lower/actual file so
frequently that i_size_read() in unionfs always failed?

Is your test
iogen01 export LTPROOT; rwtest -N iogen01 -i 120s -s read,write -Da -Dv -n 2 500b:doio.f1.$$ 1000b:doio.f2.$$
line in runtest/fs?


Junjiro Okajima

  parent reply	other threads:[~2008-06-30  4:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29  0:05 [PATCH] fsstack: fsstack_copy_inode_size locking Hugh Dickins
2008-06-29  0:07 ` [PATCH] unionfs: fix memory leak Hugh Dickins
2008-06-30 18:11   ` Erez Zadok
2008-06-29  7:15 ` [PATCH] fsstack: fsstack_copy_inode_size locking Christoph Hellwig
2008-06-29 11:56   ` Hugh Dickins
2008-06-30 18:19     ` Erez Zadok
2008-06-30 21:49       ` Michael Halcrow
2008-07-01  7:03         ` Christoph Hellwig
2008-07-02  0:00           ` Erez Zadok
2008-06-30  4:31 ` hooanon05 [this message]
2008-06-30 12:10   ` Hugh Dickins
2008-06-30 13:08     ` hooanon05

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=8725.1214800317@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=viro@zeniv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.