On Mon, Oct 28, 2013 at 05:40:30PM -0400, J. Bruce Fields wrote: > On Mon, Oct 28, 2013 at 10:57:25AM -0400, Anna Schumaker wrote: > > This patch only implements DATA_CONTENT_HOLE support, but I tried to > > write it so other arms of the discriminated union can be added easily > > later. > > And there's an NFS4ERR_UNION_NOTSUPP to handle that case, OK. (Though > the spec language is a little ambiguous: > > If the client asks for a hole and the server does not support > that arm of the discriminated union, but does support one or > more additional arms, it can signal to the client that it > supports the operation, but not the arm with > NFS4ERR_UNION_NOTSUPP. Where is this language coming from? Seems like the latest document in NFSv4.2/ repo still calls WRITE_PLUS INITIALIZE and doesn't have anything content related, just a weird "ADB" concept. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
