On 08/12/2018 10:45 AM, Tariq Toukan wrote:
>
>
> On 20/07/2018 12:36 AM, Alexei Starovoitov wrote:
>> On Wed, Jul 18, 2018 at 05:13:54PM +0300, Tariq Toukan wrote:
>>>
>>>
>>> On 17/07/2018 10:27 PM, Daniel Borkmann wrote:
On 07/17/2018 06:47 PM, Alexei Starovoitov wrote:
> On Tue, Jul
On 20/07/2018 12:36 AM, Alexei Starovoitov wrote:
On Wed, Jul 18, 2018 at 05:13:54PM +0300, Tariq Toukan wrote:
On 17/07/2018 10:27 PM, Daniel Borkmann wrote:
On 07/17/2018 06:47 PM, Alexei Starovoitov wrote:
On Tue, Jul 17, 2018 at 06:10:38PM +0300, Tariq Toukan wrote:
Fix the warning b
On Wed, Jul 18, 2018 at 05:13:54PM +0300, Tariq Toukan wrote:
>
>
> On 17/07/2018 10:27 PM, Daniel Borkmann wrote:
> > On 07/17/2018 06:47 PM, Alexei Starovoitov wrote:
> > > On Tue, Jul 17, 2018 at 06:10:38PM +0300, Tariq Toukan wrote:
> > > > Fix the warning below by calling rhashtable_lookup u
On 17/07/2018 10:27 PM, Daniel Borkmann wrote:
On 07/17/2018 06:47 PM, Alexei Starovoitov wrote:
On Tue, Jul 17, 2018 at 06:10:38PM +0300, Tariq Toukan wrote:
Fix the warning below by calling rhashtable_lookup under
RCU read lock.
...
mutex_lock(&mem_id_lock);
+ rcu_read_lock
On 07/17/2018 06:47 PM, Alexei Starovoitov wrote:
> On Tue, Jul 17, 2018 at 06:10:38PM +0300, Tariq Toukan wrote:
>> Fix the warning below by calling rhashtable_lookup under
>> RCU read lock.
>>
>> [ 342.450870] WARNING: suspicious RCU usage
>> [ 342.455856] 4.18.0-rc2+ #17 Tainted: G O
On Tue, Jul 17, 2018 at 06:10:38PM +0300, Tariq Toukan wrote:
> Fix the warning below by calling rhashtable_lookup under
> RCU read lock.
>
> [ 342.450870] WARNING: suspicious RCU usage
> [ 342.455856] 4.18.0-rc2+ #17 Tainted: G O
> [ 342.462210] -
> [ 342
Fix the warning below by calling rhashtable_lookup under
RCU read lock.
[ 342.450870] WARNING: suspicious RCU usage
[ 342.455856] 4.18.0-rc2+ #17 Tainted: G O
[ 342.462210] -
[ 342.467202] ./include/linux/rhashtable.h:481 suspicious
rcu_dereference_check(