public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0
Date: 18 Dec 2003 00:50:44 -0500	[thread overview]
Message-ID: <shsekv2ptcb.fsf@guts.uio.no> (raw)
In-Reply-To: <20031217211516.2c578bab.akpm@osdl.org>


Congratulations Linus and Andrew...

Will you be posting a plan for how you want the 2.6.x series to
proceed? I gather I'm not alone in having a load of patches that I'd
like to send you ASAP...

Here's a brief commentary on the NFS client related sections in your 2
todo lists, as well as on outstanding client issues:

Must fix:
  - The mmap-versus-truncate NFS problem appears to be a lot more
    difficult to reproduce these days. I need a call for testing to
    verify that the problem still exists.
  - I'm mystified by Andi's comments about RPC having lots of
    uninterruptible waits. It sounds to me as if he is confusing the
    "soft" and "intr" options. The two are very distinct...

Should fix:
  - The VFS support for atomic open() has already been merged by Linus
    (as well as the NFSv2/v3 support). I still have a couple of
    trivial bugfixes for the VFS case (one place where we used O_READ
    instead of FMODE_READ, and one place where the "intent" is not
    filled in at all). NFSv4 support needs for atomic open to be
    merged in (this will fix several NFSv4 file creation races).


Not listed in either:
  - There are a few lockd fixes that need to be forward-ported from
    2.4.x.

  - A *lot* of progress has been made on the NFSv4 client. I would
    very much like to merge this into 2.6.x ASAP, since it concerns
    rather critical subjects such as adding support for locking, and
    reboot recovery (as well as lots of stability fixes). What are
    your feelings on a timeframe for this sort of thing?

  - The RPCSEC_GSS support for NFSv2/v3 was merged in before it had
    been thoroughly tested and reviewed. It contains a couple of
    serious bugs that need to be ironed out.

If you want info beyond this mail, then my current set of NFS client
patches may be found on

   http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.0-test11

The file HEADER.html contains a list of patches and a brief
description of what each patch does. That should give an idea of how
much is currently outstanding (I still expect the list to continue
growing - I'm still working on several NFSv4 subtopics).

Cheers,
  Trond

  parent reply	other threads:[~2003-12-18  5:50 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18  4:14 Linux 2.6.0 Linus Torvalds
2003-12-18  4:50 ` Jonathan Brown
2003-12-18  5:00 ` Gerardo Exequiel Pozzi
2003-12-18  5:05 ` Joshua Kwan
2003-12-18  5:07 ` Norberto Bensa
2003-12-18  5:15 ` Andrew Morton
2003-12-18  5:31   ` Jeff Garzik
2003-12-18  5:50   ` Trond Myklebust [this message]
2003-12-18  6:14     ` Andrew Morton
2003-12-18  6:41       ` Trond Myklebust
2003-12-18  9:12   ` ismail 'cartman' dönmez
2003-12-18  9:34     ` Greg KH
2003-12-18  9:48     ` Maciej Soltysiak
2003-12-18  9:59       ` Matt H.
2003-12-18 10:19         ` Jens Axboe
2003-12-18 11:00           ` Maciej Soltysiak
2003-12-18 10:43       ` Hans Reiser
2003-12-18 11:03         ` reiser4 in 2.6 was " Maciej Soltysiak
2003-12-18 11:42           ` Hans Reiser
2003-12-19 17:58             ` E. Gryaznova
2003-12-18 16:17       ` bill davidsen
2003-12-18 19:31         ` Hans Reiser
2003-12-18 19:42           ` Jens Axboe
2003-12-18 22:48             ` Ed Tomlinson
2003-12-19  3:42             ` Hans Reiser
2003-12-19  6:57               ` Jens Axboe
2003-12-18  9:17   ` Marcel Holtmann
2003-12-18 13:43     ` Joseph Pingenot
2003-12-18 16:22       ` Andrew Morton
2003-12-18 21:02         ` List of mailing lists (was Re: Linux 2.6.0) Rob Landley
2003-12-18 14:21   ` Linux 2.6.0 Michael Hunold
2003-12-18 19:45   ` MD Raid fixed? was: " Mike Fedyk
2003-12-18 21:49     ` Neil Brown
2003-12-18  5:48 ` Krishna Akella
2003-12-18  7:16 ` Gabor MICSKO
2003-12-18  7:25 ` Clemens Schwaighofer
2003-12-18  9:56 ` Andrew Walrond
2003-12-18 10:20   ` Carlos Jiménez
2003-12-18 12:34 ` iain d broadfoot
2003-12-19  2:18 ` Diskstats inconsistancy between 2.4.23 & 2.6 was: " Mike Fedyk
2003-12-19  2:32   ` William Lee Irwin III
2003-12-19  3:03     ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2003-12-18  5:24 Shawn Starr
2003-12-18 18:12 (->surya<-) 
2003-12-18 23:16 Jean Tourrilhes
2003-12-19  0:31 ` Martin Diehl
2003-12-19  1:01   ` Jean Tourrilhes

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=shsekv2ptcb.fsf@guts.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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