Re: [PATH v3 1/5] nfsd41: handle current stateid in open and close

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 12, 2011 at 5:04 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
> On Mon, Dec 12, 2011 at 05:21:08PM +0200, Benny Halevy wrote:
>> On 2011-12-11 18:41, Tigran Mkrtchyan wrote:
>> > @@ -1411,9 +1441,11 @@ static struct nfsd4_operation nfsd4_ops[] = {
>> >     },
>> >     [OP_CLOSE] = {
>> >             .op_func = (nfsd4op_func)nfsd4_close,
>> > -           .op_flags = OP_MODIFIES_SOMETHING,
>> > +           .op_flags = OP_MODIFIES_SOMETHING | CONSUMES_CURRENT_STATEID,
>>
>> Looks like this also requires PROVIDES_CURRENT_STATEID
>> (or just ditch the flag so there can't be disagreement between the two :)
>
> Please, yes, let's just eliminate the redundant flags.

Fine with me.

Tigran.
>
> --b.
> --
> 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
--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux