From: Greg Kurz <groug@kaod.org>
To: Dominique Martinet <dominique.martinet@cea.fr>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
v9fs-developer@lists.sourceforge.net,
Ron Minnich <rminnich@sandia.gov>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] fs/9p: fix setattr/getattr issues with open files
Date: Mon, 4 Jul 2016 17:08:49 +0200 [thread overview]
Message-ID: <20160704170849.1654d6a0@bahia.lan> (raw)
In-Reply-To: <20160704141655.GA5799@u-isr-cdi-08>
On Mon, 4 Jul 2016 16:16:55 +0200
Dominique Martinet <dominique.martinet@cea.fr> wrote:
> I *think* this introduces a race somewhere, I'm getting errors like:
> cat: f.05: No such file or directory
> cat: f.14: No such file or directory
> cat: f.13: No such file or directory
> cat: f.39: No such file or directory
> cat: f.05: No such file or directory
>
>
> when doing:
> for file in {01..50}; do touch f.${file}; done
> seq 1 1000 | xargs -n 1 -P 25 -I{} cat f.* > /dev/null
>
>
>
> I don't get it everytime but close enough to. Server is bi-socket and
> has some numa effects which help producing data-synchronization races,
> it's probably harder to hit on a laptop.
>
> I'm simply trying over a patched qemu for now, applied patches right on
> top of 4.6.1, can't seem to reproduce with a vanilla 4.6.1 without any
> change to qemu (still patched), so it looks kernel-side.
>
>
> Can't say I've taken much time to look at the patches yet though,
> sorry - I don't think it's too hard to debug though so I'll take a look
> tomorrow as soon as I find time if you haven't gotten it by then.
>
Hi Dominique !
Thanks a lot for your testing. I'll try to reproduce on my POWER8 system.
Cheers.
--
Greg
next prev parent reply other threads:[~2016-07-04 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 12:25 [Qemu-devel] [PATCH 0/3] fs/9p: fix setattr/getattr issues with open files Greg Kurz
2016-06-22 12:25 ` [Qemu-devel] [PATCH 1/3] fs/9p: fix create-unlink-getattr idiom Greg Kurz
2016-06-22 12:25 ` [Qemu-devel] [PATCH 2/3] fs/9p: track open fids Greg Kurz
2016-06-22 12:25 ` [Qemu-devel] [PATCH 3/3] fs/9p: search open fids first Greg Kurz
2016-07-04 14:16 ` [Qemu-devel] [PATCH 0/3] fs/9p: fix setattr/getattr issues with open files Dominique Martinet
2016-07-04 15:08 ` Greg Kurz [this message]
2016-07-07 12:35 ` Dominique Martinet
2016-07-07 13:34 ` Greg Kurz
2016-07-08 17:04 ` Greg Kurz
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=20160704170849.1654d6a0@bahia.lan \
--to=groug@kaod.org \
--cc=davem@davemloft.net \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=qemu-devel@nongnu.org \
--cc=rminnich@sandia.gov \
--cc=v9fs-developer@lists.sourceforge.net \
/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).