Re: [PATCH 1/2] NFSv4: Fix CLOSE races with OPEN

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

 



On 14 Feb 2018, at 10:29, Trond Myklebust wrote:
> On Wed, 2018-02-14 at 10:21 -0500, Jeff Layton wrote:
>> On Wed, 2018-02-14 at 10:05 -0500, Benjamin Coddington wrote:
>>> Hi Olga,
>>>
>>> On 13 Feb 2018, at 15:08, Olga Kornievskaia wrote:
>>>
>>>> On Mon, Nov 14, 2016 at 11:19 AM, Trond Myklebust
>>>> <trond.myklebust@xxxxxxxxxxxxxxx> wrote:
>>>> ...
>>> Ah, good question there..  Even though the stateid is not useful
>>> for
>>> operations that follow, I think the sequenceid should be
>>> incremented because
>>> the CLOSE is an operation that modifies the set of locks or state:
>>>
>>
>> It doesn't matter.

Yes, good condensed point.  It doesn't matter.

>>> ...
> Is there a proposal to change the current client behaviour here? As far
> as I can tell, the answer is "no". Am I missing something?

Not that I can see.  I think we're just comparing linux and netapp server
behaviors..

Ben
--
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