From: Nick Piggin <npiggin@suse.de>
To: David Chinner <dgc@sgi.com>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Mark Fasheh <mark.fasheh@oracle.com>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [ANNOUNCE] new new aops patchset
Date: Thu, 5 Apr 2007 05:00:44 +0200 [thread overview]
Message-ID: <20070405030044.GF11192@wotan.suse.de> (raw)
In-Reply-To: <20070405024350.GL32602149@melbourne.sgi.com>
On Thu, Apr 05, 2007 at 12:43:50PM +1000, David Chinner wrote:
> On Thu, Apr 05, 2007 at 10:10:18AM +1000, David Chinner wrote:
> > On Mon, Apr 02, 2007 at 02:09:34PM +0200, Nick Piggin wrote:
> > > Updated aops patchset against 2.6.21-rc5.
> > >
> > > http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
> > >
> > > Files/dirs are 2.6.21-rc5-new-aops*
> > >
> > > Contains numerous fixes from Mark and myself -- I'd say the core code is
> > > getting reasonably stable at this point.
> > ......
> >
> > > (compile only) patches for NFS, XFS, FUSE, eCryptfs. OK, they're untested,
> >
> > Failed to compile in UDF and reiser for me, but no doubt you know
> > that already. Don't have time to look at why - I just disabled them
> > so I get some QA done on the XFS and core changes.
>
> Nick - the XFSQA randholes test locks up. As you can probably guess
> it creates holey files and does stuff to them ;)
>
> Both pdflush and a write doing an a blocked waiting for a page to become unlocked.
> They are both waiting on teh same page (0xa0007fffffe8bd68).
[...]
> So the page is locked and it has a delalloc buffer on it that used to
> be a hole. The problem page is at EOF....
>
> No idea what is going write yet.....
OK, thanks for testing. This is with the full patchset applied, I guess.
No real ideas here (brute force we put a last-locked stack trace into
struct page :P), but I wonder if it may be any of my earlier patches?
(ie. not the new aops path or XFS conversion itself).
Anyway I think randholes is available online, right? I'll try reproduce
here and help.
Thanks,
Nick
next prev parent reply other threads:[~2007-04-05 3:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 12:09 [ANNOUNCE] new new aops patchset Nick Piggin
2007-04-02 20:18 ` Badari Pulavarty
2007-04-03 0:45 ` Nick Piggin
2007-04-02 20:44 ` Badari Pulavarty
2007-04-02 23:58 ` Nick Piggin
2007-04-03 15:59 ` Badari Pulavarty
2007-04-04 2:33 ` Nick Piggin
2007-04-02 21:44 ` Badari Pulavarty
2007-04-02 23:08 ` Badari Pulavarty
2007-04-02 23:14 ` Badari Pulavarty
2007-04-02 23:49 ` Nick Piggin
2007-04-03 15:57 ` Badari Pulavarty
2007-04-04 2:31 ` Nick Piggin
2007-04-02 23:31 ` Badari Pulavarty
2007-04-02 23:35 ` Nick Piggin
2007-04-02 23:56 ` Badari Pulavarty
2007-04-03 0:02 ` Nick Piggin
2007-04-03 0:00 ` Badari Pulavarty
2007-04-03 0:08 ` Nick Piggin
2007-04-03 9:31 ` Nick Piggin
2007-04-03 16:03 ` Badari Pulavarty
2007-04-04 2:37 ` Nick Piggin
2007-04-03 17:35 ` Badari Pulavarty
2007-04-04 3:05 ` Nick Piggin
2007-04-04 22:10 ` Mark Fasheh
2007-04-04 22:39 ` Badari Pulavarty
2007-04-04 22:51 ` Mark Fasheh
2007-04-04 23:02 ` Badari Pulavarty
2007-04-04 23:05 ` Badari Pulavarty
2007-04-04 23:17 ` Mark Fasheh
2007-04-04 23:32 ` Badari Pulavarty
2007-04-05 2:08 ` Nick Piggin
2007-04-05 15:21 ` Badari Pulavarty
2007-04-06 1:38 ` Nick Piggin
2007-04-05 2:09 ` Nick Piggin
2007-04-05 0:10 ` David Chinner
2007-04-05 2:13 ` Nick Piggin
2007-04-05 7:45 ` Christoph Hellwig
2007-04-05 7:58 ` Nick Piggin
2007-04-05 2:43 ` David Chinner
2007-04-05 3:00 ` Nick Piggin [this message]
2007-04-05 6:18 ` David Chinner
2007-04-05 6:40 ` Nick Piggin
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=20070405030044.GF11192@wotan.suse.de \
--to=npiggin@suse.de \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=swhiteho@redhat.com \
/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).