On 23/02/17 13:08, Bob Peterson wrote:
- Original Message -
| On 22/02/17 19:19, Bob Peterson wrote:
| > - Original Message -
| > | From: Andrew Price
| > |
| > | We must hold the rcu read lock across looking up glocks and trying to
| > | bump their refcount to prevent the glocks
- Original Message -
| On 22/02/17 19:19, Bob Peterson wrote:
| > - Original Message -
| > | From: Andrew Price
| > |
| > | We must hold the rcu read lock across looking up glocks and trying to
| > | bump their refcount to prevent the glocks from being freed in between.
| > |
| > |
On 22/02/17 19:19, Bob Peterson wrote:
- Original Message -
| From: Andrew Price
|
| We must hold the rcu read lock across looking up glocks and trying to
| bump their refcount to prevent the glocks from being freed in between.
|
| Signed-off-by: Andreas Gruenbacher
| ---
Hi,
Thanks. T
- Original Message -
| From: Andrew Price
|
| We must hold the rcu read lock across looking up glocks and trying to
| bump their refcount to prevent the glocks from being freed in between.
|
| Signed-off-by: Andreas Gruenbacher
| ---
Hi,
Thanks. This is now applied to the for-next bran
Hi,
On 22/02/17 15:34, Andreas Gruenbacher wrote:
On Wed, Feb 22, 2017 at 4:29 PM, Steven Whitehouse wrote:
There should be no need to retry at all. Either the new entry will be added
to the hash table, or it will find an existing entry in the table. Is there
really some way this can fail for
On Wed, Feb 22, 2017 at 4:29 PM, Steven Whitehouse wrote:
> There should be no need to retry at all. Either the new entry will be added
> to the hash table, or it will find an existing entry in the table. Is there
> really some way this can fail for some reason?
Yes, we may find an existing entry
Hi,
On 22/02/17 15:26, Andreas Gruenbacher wrote:
On Wed, Feb 22, 2017 at 4:13 PM, Steven Whitehouse wrote:
Hi,
Looks good, but can we fix that "retry for 100 times" loop too at the same
time? There does appear to be an rhashtable API function that does what we
need there,
The rhashtable cl
On Wed, Feb 22, 2017 at 4:26 PM, Andreas Gruenbacher
wrote:
> On Wed, Feb 22, 2017 at 4:13 PM, Steven Whitehouse
> wrote:
>> Hi,
>>
>> Looks good, but can we fix that "retry for 100 times" loop too at the same
>> time? There does appear to be an rhashtable API function that does what we
>> need
On Wed, Feb 22, 2017 at 4:13 PM, Steven Whitehouse wrote:
> Hi,
>
> Looks good, but can we fix that "retry for 100 times" loop too at the same
> time? There does appear to be an rhashtable API function that does what we
> need there,
The rhashtable cleanup which I've posted separately doesn't act
On 22/02/17 15:09, Andreas Gruenbacher wrote:
From: Andrew Price
We must hold the rcu read lock across looking up glocks and trying to
bump their refcount to prevent the glocks from being freed in between.
Signed-off-by: Andreas Gruenbacher
Signed-off-by: Andrew Price
Thanks,
Andy
---
Hi,
Looks good, but can we fix that "retry for 100 times" loop too at the
same time? There does appear to be an rhashtable API function that does
what we need there,
Steve.
On 22/02/17 15:09, Andreas Gruenbacher wrote:
From: Andrew Price
We must hold the rcu read lock across looking up gl
From: Andrew Price
We must hold the rcu read lock across looking up glocks and trying to
bump their refcount to prevent the glocks from being freed in between.
Signed-off-by: Andreas Gruenbacher
---
fs/gfs2/glock.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/gfs2/glock.c b/fs/g
12 matches
Mail list logo
