From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tao Guo <glorioustao@gmail.com>
Cc: Zhang Jingwang <yyalone@gmail.com>,
Boaz Harrosh <bharrosh@panasas.com>,
Benny Halevy <bhalevy@panasas.com>,
Zhang Jingwang
<zhangjingwang-U4AKAne5IzAR5TUyvShJeg@public.gmane.org>,
linux-nfs@vger.kernel.org, iisaman@netapp.com
Subject: Re: [PATCH] pnfsblock: Lookup list entry of layouts and tags in reverse order
Date: Wed, 19 May 2010 17:38:49 -0400 [thread overview]
Message-ID: <20100519213849.GR9720@fieldses.org> (raw)
In-Reply-To: <20100519163632.GL4581@fieldses.org>
On Wed, May 19, 2010 at 12:36:32PM -0400, J. Bruce Fields wrote:
> On Wed, May 19, 2010 at 12:56:42PM +0800, Tao Guo wrote:
> > I think the warning just indicate a possible bug:
> > nfs_inode_set_delegation():
> > clp->cl_lock
> > --> inode->i_lock
> > get_lock_alloc_layout():
> > nfsi->lo_lock
> > --> clp->cl_lock
> > nfs_try_to_update_request()->pnfs_do_flush()->_pnfs_do_flush()->
> > pnfs_find_get_lseg()->get_lock_current_layout():
> >
> > inode->i_lock
> >
> > -->nfsi->lo_lock
> > In nfs_inode_set_delegation(), maybe we should unlock clp->cl_lock before
> > taking inode->i_lock spinlock?
> >
> > PS: I just use the latest pnfsblock code(pnfs-all-2.6.34-2010-05-17) doing some
> > basic r/w tests and it works fine.
>
> Could you try running the connectathon general test?
>
> > Can you find out which code path
> > lead to IO errror?
>
> I'll try to narrow down the test case.
I haven't gotten the chance to narrow it down any more. So all I can
say is that:
~/cthon04# NFSTESTDIR=/mnt/TMP ./runtests -g
GENERAL TESTS: directory /mnt/TMP
if test ! -x runtests; then chmod a+x runtests; fi
cd /mnt/TMP; rm -f Makefile runtests runtests.wrk *.sh *.c
mkdummy rmdummy nroff.in makefile.tst
cp Makefile runtests runtests.wrk *.sh *.c mkdummy rmdummy
nroff.in makefile.tst /mnt/TMP
Small Compile
runtests.wrk: 63: ./stat: Input/output error
general tests failed
is a consistent result for me. (Using the tests from
http://www.connectathon.org/nfstests.html.)
--b.
next prev parent reply other threads:[~2010-05-19 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 3:36 [PATCH] pnfsblock: Lookup list entry of layouts and tags in reverse order Zhang Jingwang
[not found] ` <20100510033610.GA5443-nK6E9TRyOkVSq9BJjBFyUp/QNRX+jHPU@public.gmane.org>
2010-05-12 6:46 ` Benny Halevy
2010-05-12 20:28 ` J. Bruce Fields
2010-05-17 13:53 ` J. Bruce Fields
2010-05-17 14:24 ` Boaz Harrosh
2010-05-17 14:53 ` J. Bruce Fields
2010-05-17 16:53 ` J. Bruce Fields
2010-05-17 17:22 ` Zhang Jingwang
[not found] ` <AANLkTilUpAHrtHH8pauvYrAuD3rWgj7aDmrTOzrmU-h5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-18 16:20 ` J. Bruce Fields
2010-05-19 4:56 ` Tao Guo
[not found] ` <AANLkTik9L15tqpSboBpb9cSTy3hVPLEK487w94pEbLrS-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-19 16:36 ` J. Bruce Fields
2010-05-19 21:38 ` J. Bruce Fields [this message]
2010-05-20 5:44 ` Tao Guo
2010-05-21 23:00 ` J. Bruce Fields
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=20100519213849.GR9720@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=glorioustao@gmail.com \
--cc=iisaman@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=yyalone@gmail.com \
--cc=zhangjingwang-U4AKAne5IzAR5TUyvShJeg@public.gmane.org \
/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.