From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [pnfs] Linux pNFS status meeting 04/29
Date: Thu, 29 Apr 2010 14:43:11 -0400 [thread overview]
Message-ID: <20100429184311.GB4194@fieldses.org> (raw)
In-Reply-To: <20100429173902.GE1654@fieldses.org>
On Thu, Apr 29, 2010 at 01:39:03PM -0400, J. Bruce Fields wrote:
> 1. upstream status/merge plans (trond, bfields)
> - 2.6.34-rc5
> - server: merged one 2.6.34 bugfix, some more bugfixes/cleanup for
> 2.6.35, no new features merged.
> - client: bunch of bugfixes:
> - writeback code fixes:
> - race with commit
> - nfs_setup_writeback BUG_ON()
> - other than that, misc. NULL/ERR-mixups.
> - Andy notes he's been seeing bigfile blocked for >= 30
> seconds; Trond says that's probably due to the commit
> race above.
>
> 2. State of pNFS tree (bhalevy)
> - forwarded-ported to -rc5, released a few minutes ago. Passes
> cthon cleanly (thanks to commit race fix).
> - merged some other patches.
>
> 3. Mailing list change
> - consolidated pnfs and nfsv4 lists to linux-nfs@vger.kernel.org
> - kernel.org appears to be having trouble; bfields will
> investigate.
As far as I can tell, from my mail and from public archives, the
kernel.org mailing lists just aren't working right now.
So for now I'm inclined to assume someobody's already working on it and
hope it'll be fixed soon....
Bad timing with the change, though!
--b.
next prev parent reply other threads:[~2010-04-30 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF9FD7A126.8253DE0C-ON88257714.00106772-88257714.00108527@us.ibm.com>
2010-04-29 14:46 ` [pnfs] Linux pNFS status meeting 04/29 J. Bruce Fields
2010-04-29 17:39 ` J. Bruce Fields
2010-04-29 18:43 ` J. Bruce Fields [this message]
2010-04-30 22:03 ` 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=20100429184311.GB4194@fieldses.org \
--to=bfields@fieldses.org \
--cc=eshel@almaden.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox