From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Monam Agarwal <monamagarwal123@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/input: Use RCU_INIT_POINTER(x, NULL) in evdev.c
Date: Wed, 26 Mar 2014 13:30:05 -0700 [thread overview]
Message-ID: <20140326203005.GC11013@core.coreip.homeip.net> (raw)
In-Reply-To: <1395599177-6776-1-git-send-email-monamagarwal123@gmail.com>
Hi Monam,
On Sun, Mar 23, 2014 at 11:56:17PM +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)
Logically speaking we perform assignment, not initialization there.
Since we are not in hot path I think we should leave the code as is.
Thanks.
>
> Signed-off-by: Monam Agarwal <monamagarwal123@gmail.com>
> ---
> drivers/input/evdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index a06e125..fffa107 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -291,7 +291,7 @@ static int evdev_ungrab(struct evdev *evdev, struct evdev_client *client)
> if (grab != client)
> return -EINVAL;
>
> - rcu_assign_pointer(evdev->grab, NULL);
> + RCU_INIT_POINTER(evdev->grab, NULL);
> synchronize_rcu();
> input_release_device(&evdev->handle);
>
> --
> 1.7.9.5
>
--
Dmitry
prev parent reply other threads:[~2014-03-26 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 18:26 [PATCH] drivers/input: Use RCU_INIT_POINTER(x, NULL) in evdev.c Monam Agarwal
2014-03-26 20:30 ` Dmitry Torokhov [this message]
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=20140326203005.GC11013@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monamagarwal123@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).