On 05/06/2013 06:53 PM, James Bottomley wrote:
On Sat, 2013-05-04 at 07:17 +0300, Ric Wheeler wrote:
On 05/02/2013 08:18 PM, Steve Dickson wrote:
From: Steve Dickson <steved@xxxxxxxxxx>
Here is an the next rlease of the label NFS patches
ported to the linux-3.9 release
The following changes were made from the previous release.
(Note, only the server patch changed in this release)
* Remove the buffer overflow in the allocation of labels.
* Removed needless char * casting
* Removed the -EMSGSIZE to nfs4err_badlabel errno mapping
by changing the return value of nfsd4_label_alloc() to
be a _be32 value.
It would be great to see this patch series land in time for 3.10 - seems like a
major feature that has had been held in development for years and it does have a
very interested user base waiting for this to land.
Are there any existing roadblocks to having this make it this merge
window?
You mean other than the one Bruce and Trond already mentioned and which
you presumably already read? i.e. it's a large feature whose final
incarnation landed when the merge window was already open which by
process should receive incubation in linux-next before being merged.
It is entirely within the gift of the maintainers to vary the incubation
requirements, but if they do and it comes back with a ton of problems
from the 0 day project or smatch or even a build failure that would have
been picked up by linux-next, they'll be at the wrong end of Linus'
flame thrower not you. So it is rather unfair to pressure the
maintainers like this.
Kernel processes exist for a reason and almost every maintainer has the
scars that remind them of this.
James
Don't worry James - this one has had at least as much testing as the average
SCSI driver update :)
This is was not meant as pressure, James Morris (not you) had replied that his
patches are ready and he expected them to be pulled via the NFS trees.
This was meant to facilitate getting this multi-tree, multi-maintainer series
ready to merge and make sure we aren't stuck each waiting for a response from
the next person in the loop.
Note that this patch set has been in development for *years*, been tested at
connectathon, tested by interested parties who promoted the earliest versions of
the patches and tested by RHEL (of course, the series has evolved over time).
Ric
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
