[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161102171149.kl66dlmlrc44zock@linutronix.de>
Date: Wed, 2 Nov 2016 18:11:49 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Trond Myklebust <trondmy@...marydata.com>
Cc: Schumaker Anna <anna.schumaker@...app.com>,
List Linux NFS Mailing <linux-nfs@...r.kernel.org>,
List Linux Kernel Mailing <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [PATCH v3] NFSv4: replace seqcount_t with a rw_semaphore
On 2016-10-31 16:11:02 [+0000], Trond Myklebust wrote:
>
> Yes, and yes. We can’t rely on the list pointers remaining correct, so we restart the list scan and we use the ops->state_flag_bit to signal whether or not state has been recovered for the entry being scanned.
but this is tested at the top of the loop and by then you look at
lists' ->next pointer which might be invalid.
Sebastian
Powered by blists - more mailing lists