From: Arend van Spriel <arend@broadcom.com>
To: Neil Horman <nhorman@tuxdriver.com>,
Monam Agarwal <monamagarwal123@gmail.com>
Cc: <rcj@linux.vnet.ibm.com>, <mhcerri@linux.vnet.ibm.com>,
<fin@linux.vnet.ibm.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/crypto: Use RCU_INIT_POINTER(x, NULL) in nx/nx-842.c
Date: Mon, 24 Mar 2014 13:03:29 +0100 [thread overview]
Message-ID: <53301F11.9030305@broadcom.com> (raw)
In-Reply-To: <20140324111606.GB19368@hmsreliant.think-freely.org>
On 24/03/14 12:16, Neil Horman wrote:
> On Mon, Mar 24, 2014 at 01:01:04AM +0530, Monam Agarwal wrote:
>> This patch replaces rcu_assign_pointer(x, NULL) with RCU_INIT_POINTER(x, NULL)
>>
>> The rcu_assign_pointer() ensures that the initialization of a structure
>> is carried out before storing a pointer to that structure.
>> And in the case of the NULL pointer, there is no structure to initialize.
>> So, rcu_assign_pointer(p, NULL) can be safely converted to RCU_INIT_POINTER(p, NULL)
>>
>> Signed-off-by: Monam Agarwal <monamagarwal123@gmail.com>
>> ---
>> drivers/crypto/nx/nx-842.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/crypto/nx/nx-842.c b/drivers/crypto/nx/nx-842.c
>> index 1e5481d..c4fcbf4 100644
>> --- a/drivers/crypto/nx/nx-842.c
>> +++ b/drivers/crypto/nx/nx-842.c
>> @@ -1234,7 +1234,7 @@ static int __exit nx842_remove(struct vio_dev *viodev)
>> old_devdata = rcu_dereference_check(devdata,
>> lockdep_is_held(&devdata_mutex));
>> of_reconfig_notifier_unregister(&nx842_of_nb);
>> - rcu_assign_pointer(devdata, NULL);
>> + RCU_INIT_POINTER(devdata, NULL);
>> spin_unlock_irqrestore(&devdata_mutex, flags);
>> synchronize_rcu();
>> dev_set_drvdata(&viodev->dev, NULL);
>> @@ -1285,7 +1285,7 @@ static void __exit nx842_exit(void)
>> spin_lock_irqsave(&devdata_mutex, flags);
>> old_devdata = rcu_dereference_check(devdata,
>> lockdep_is_held(&devdata_mutex));
>> - rcu_assign_pointer(devdata, NULL);
>> + RCU_INIT_POINTER(devdata, NULL);
>> spin_unlock_irqrestore(&devdata_mutex, flags);
>> synchronize_rcu();
>> if (old_devdata)
>
> This really does't seem right. rcu_assign_pointer users ACCESS_ONCE to protect
> against multiple loads that allow for concurrent read/write use with parallel
> rcu_dereference calls, whereas RCU_INIT_POINTER does not. It also just doesn't
> look right. We've already initalized the pointerin nx842_init, we don't need to
> re-initalize it here, we need to assign it to NULL.
I was being cautious as well, but Paul gave me an explanation [1]
Hope it helps you as well ;-)
But I think I also saw a patch that modifies rcu_assign_pointer to
handle NULL assignment. Don't recall the thread.
Regards,
Arend
[1] http://mid.gmane.org/20140320150601.GK4405@linux.vnet.ibm.com
>
> Neil
>
>> --
>> 1.7.9.5
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-03-24 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 19:31 [PATCH] drivers/crypto: Use RCU_INIT_POINTER(x, NULL) in nx/nx-842.c Monam Agarwal
2014-03-24 11:16 ` Neil Horman
2014-03-24 12:03 ` Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-23 19:32 Monam Agarwal
2014-04-16 13:48 ` Herbert Xu
2014-03-22 20:40 Monam Agarwal
2014-03-22 20:34 Monam Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53301F11.9030305@broadcom.com \
--to=arend@broadcom.com \
--cc=davem@davemloft.net \
--cc=fin@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhcerri@linux.vnet.ibm.com \
--cc=monamagarwal123@gmail.com \
--cc=nhorman@tuxdriver.com \
--cc=rcj@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.