From: NeilBrown <neilb@cse.unsw.edu.au>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: nfs@lists.sourceforge.net
Subject: [PATCH kNFSd 0 of 4] Introduction
Date: Mon, 16 Aug 2004 13:58:43 +1000 [thread overview]
Message-ID: <20040816135256.9819.patches@notabene> (raw)
4 patches for knfsd. in 2.4.28-pre1
1/ improve checking of out-of-range lengths, particularly in write requests.
2/ make CONFIG_NFSD_TCP non-EXPERIMENTAL and select it by default.
3/ Allow a larger blocksize on arch's with large page size.
4/ use llseek instead of explicitly setting f_pos in NFS i/o requests.
Thank,
NeilBrown
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-08-16 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 3:58 NeilBrown [this message]
2004-08-16 3:58 ` [PATCH kNFSd 2 of 4] mark NFS/TCP not EXPERIMENTAL NeilBrown
2004-08-16 3:58 ` [PATCH kNFSd 4 of 4] Use llseek instead of f_pos= for directory seeking NeilBrown
2004-08-16 9:21 ` Christoph Hellwig
2004-08-16 9:23 ` Christoph Hellwig
2004-08-16 3:58 ` [PATCH kNFSd 3 of 4] Allow larger NFSd MAXBLKSIZE on architectures with larger PAGE_SIZE NeilBrown
2004-08-16 3:58 ` [PATCH kNFSd 1 of 4] Fixed possibly xdr parsing error if write size exceed 2^31 NeilBrown
2005-07-11 9:50 ` Olaf Kirch
2005-07-12 6:42 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-08-20 6:51 [PATCH kNFSd 0 of 4] Introduction NeilBrown
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=20040816135256.9819.patches@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=marcelo.tosatti@cyclades.com \
--cc=nfs@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 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.