From: "Paul E. McKenney" <paulmck@kernel.org>
To: qiang.zhang@windriver.com
Cc: akpm@linux-foundation.org, manfred@colorfullife.com,
gustavoars@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipc/sem.c: Convert kfree_rcu() to call_rcu() in freeary function
Date: Wed, 30 Dec 2020 08:19:41 -0800 [thread overview]
Message-ID: <20201230161941.GN2657@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20201230120038.19489-1-qiang.zhang@windriver.com>
On Wed, Dec 30, 2020 at 08:00:38PM +0800, qiang.zhang@windriver.com wrote:
> From: Zqiang <qiang.zhang@windriver.com>
>
> Due to freeary function is called with spinlock be held,
> the synchronize_rcu function may be called in kfree_rcu
> function, the schedule may be happen in spinlock critical
> region, need to replace kfree_rcu() with call_rcu().
Except that the call to kfree_rcu() below has two arguments, and thus
provides a link for queuing the callback. It will never directly invoke
synchronize_rcu(). It is only the single-argument variant of kfree_rcu()
that might invoke synchronize_rcu().
Or are you seeing lockdep or might-sleep failures with the current code?
If so, please post the relevant portions of the console output.
Thanx, Paul
> Fixes: 693a8b6eecce ("ipc,rcu: Convert call_rcu(free_un) to kfree_rcu()")
> Signed-off-by: Zqiang <qiang.zhang@windriver.com>
> ---
> ipc/sem.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/ipc/sem.c b/ipc/sem.c
> index f6c30a85dadf..12c3184347d9 100644
> --- a/ipc/sem.c
> +++ b/ipc/sem.c
> @@ -1132,6 +1132,13 @@ static int count_semcnt(struct sem_array *sma, ushort semnum,
> return semcnt;
> }
>
> +static void free_un(struct rcu_head *head)
> +{
> + struct sem_undo *un = container_of(head, struct sem_undo, rcu);
> +
> + kfree(un);
> +}
> +
> /* Free a semaphore set. freeary() is called with sem_ids.rwsem locked
> * as a writer and the spinlock for this semaphore set hold. sem_ids.rwsem
> * remains locked on exit.
> @@ -1152,7 +1159,7 @@ static void freeary(struct ipc_namespace *ns, struct kern_ipc_perm *ipcp)
> un->semid = -1;
> list_del_rcu(&un->list_proc);
> spin_unlock(&un->ulp->lock);
> - kfree_rcu(un, rcu);
> + call_rcu(&un->rcu, free_un);
> }
>
> /* Wake up all pending processes and let them fail with EIDRM. */
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-12-30 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 12:00 qiang.zhang
2020-12-30 16:19 ` Paul E. McKenney [this message]
2020-12-31 0:56 ` 回复: " Zhang, Qiang
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=20201230161941.GN2657@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=qiang.zhang@windriver.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
all inboxes | Powered by JetHome®