rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Ziwei Dai <ziwei.dai@unisoc.com>, <urezki@gmail.com>,
	<paulmck@kernel.org>, <frederic@kernel.org>,
	<quic_neeraju@quicinc.com>, <josh@joshtriplett.org>,
	<rostedt@goodmis.org>, <mathieu.desnoyers@efficios.com>,
	<jiangshanlai@gmail.com>, <joel@joelfernandes.org>,
	<rcu@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <shuang.wang@unisoc.com>,
	<yifan.xin@unisoc.com>, <ke.wang@unisoc.com>,
	<xuewen.yan@unisoc.com>, <zhiguo.niu@unisoc.com>,
	<zhaoyang.huang@unisoc.com>
Subject: Re: [PATCH V2] rcu: Make sure new krcp free business is handled after the wanted rcu grace period.
Date: Mon, 3 Apr 2023 19:31:31 +0530	[thread overview]
Message-ID: <eaf6dd0c-3402-56bd-8b58-9275b5025032@quicinc.com> (raw)
In-Reply-To: <1680266529-28429-1-git-send-email-ziwei.dai@unisoc.com>



On 3/31/2023 6:12 PM, Ziwei Dai wrote:
> In kfree_rcu_monitor(), new free business at krcp is attached to any free
> channel at krwp. kfree_rcu_monitor() is responsible to make sure new free
> business is handled after the rcu grace period. But if there is any none-free
> channel at krwp already, that means there is an on-going rcu work,
> which will cause the kvfree_call_rcu()-triggered free business is done
> before the wanted rcu grace period ends.
> 
> This commit ignore krwp which has non-free channel at kfree_rcu_monitor(),
> to fix the issue that kvfree_call_rcu() loses effectiveness.
> 
> Below is the css_set obj "from_cset" use-after-free case caused by
> kvfree_call_rcu() losing effectiveness.
> CPU 0 calls rcu_read_lock(), then use "from_cset", then hard irq comes,
> the task is schedule out.
> CPU 1 calls kfree_rcu(cset, rcu_head), willing to free "from_cset" after new gp.
> But "from_cset" is freed right after current gp end. "from_cset" is reallocated.
> CPU 0 's task arrives back, references "from_cset"'s member, which causes crash.
> 
> CPU 0					CPU 1
> count_memcg_event_mm()
> |rcu_read_lock()  <---
> |mem_cgroup_from_task()
>   |// css_set_ptr is the "from_cset" mentioned on CPU 1
>   |css_set_ptr = rcu_dereference((task)->cgroups)
>   |// Hard irq comes, current task is scheduled out.
> 
> 					cgroup_attach_task()
> 					|cgroup_migrate()
> 					|cgroup_migrate_execute()
> 					|css_set_move_task(task, from_cset, to_cset, true)
> 					|cgroup_move_task(task, to_cset)
> 					|rcu_assign_pointer(.., to_cset)
> 					|...
> 					|cgroup_migrate_finish()
> 					|put_css_set_locked(from_cset)
> 					|from_cset->refcount return 0
> 					|kfree_rcu(cset, rcu_head) // means to free from_cset after new gp
> 					|add_ptr_to_bulk_krc_lock()
> 					|schedule_delayed_work(&krcp->monitor_work, ..)
> 
> 					kfree_rcu_monitor()
> 					|krcp->bulk_head[0]'s work attached to krwp->bulk_head_free[]
> 					|queue_rcu_work(system_wq, &krwp->rcu_work)
> 					|if rwork->rcu.work is not in WORK_STRUCT_PENDING_BIT state,
> 					|call_rcu(&rwork->rcu, rcu_work_rcufn) <--- request a new gp
> 
> 					// There is a perious call_rcu(.., rcu_work_rcufn)
> 					// gp end, rcu_work_rcufn() is called.
> 					rcu_work_rcufn()
> 					|__queue_work(.., rwork->wq, &rwork->work);
> 
> 					|kfree_rcu_work()
> 					|krwp->bulk_head_free[0] bulk is freed before new gp end!!!
> 					|The "from_cset" is freed before new gp end.
> 
> // the task is scheduled in after many ms.
>   |css_set_ptr->subsys[(subsys_id) <--- Caused kernel crash, because css_set_ptr is freed.
> 

I too have observed this issue on 5.15, where i see below callstack.
And i see different view of memory and one is this callstack and the
other is,  i see proper value of memcg from the ramdump.

Looks to be different view of memory between rcu critical section.

119653.424434][T730913] binder: 30858:30913 ioctl c0306201 7633b56a78 
returned -14
[119653.426095][T730918] Unable to handle kernel paging request at 
virtual address 000000034088e7be

-000|mem_cgroup_disabled(inline)
-000|__count_memcg_events([X0] memcg = 0x000000034088D9AE, [X1] idx = 
PGFAULT = 0x11, [X2] count = 0x1)
     |  [X0] memcg = 0x000000034088D9AE
     |  [X1] idx = PGFAULT = 0x11
     |  [X2] count = 0x1
     |  [locdesc] __ptr = 0x0
-001|arch_local_irq_restore(inline)
     |  [X26] flags = 0x0
-001|count_memcg_events(inline)
     |  [X26] flags = 0x0
-001|count_memcg_event_mm(inline)
     |  [locdesc] idx = PGFAULT = 0x11
-001|do_handle_mm_fault([X24] vma = 0xFFFFFF89CC704870, [X20] address = 
0x000000763395AA78, [X22] flags =
     |  [X24] vma = 0xFFFFFF89CC704870
     |  [X20] address = 0x000000763395AA78
     |  [X22] flags = 0x0215
     |  [X23] seq = 0x0
     |  [X19] regs = 0xFFFFFFC05EA73AD0
     |  [locdesc] ret = 0x0
-002|handle_mm_fault(inline)
     |  [X22] address = 0x000000763395AA78
     |  [X24] flags = 0x0215
     |  [X21] regs = 0xFFFFFFC05EA73AD0
-002|__do_page_fault(inline)
     |  [X23] mm = 0xFFFFFF8812F65400
     |  [X22] addr = 0x000000763395AA78
     |  [X24] mm_flags = 0x0215
     |  [X27] vm_flags = 0x2
     |  [X21] regs = 0xFFFFFFC05EA73AD0
[119653.427011][T730918]  __count_memcg_events+0x2c/0x274
[119653.427014][T730918]  do_handle_mm_fault+0xe4/0x2c8
[119653.427017][T730918]  do_page_fault+0x4c0/0x688
[119653.427022][T730918]  do_translation_fault+0x48/0x64
[119653.427025][T730918]  do_mem_abort+0x68/0x148
[119653.427028][T730918]  el1_abort+0x40/0x64
[119653.427032][T730918]  el1h_64_sync_handler+0x60/0xa0
[119653.427035][T730918]  el1h_64_sync+0x7c/0x80
[119653.427037][T730918]  __arch_copy_to_user+0x60/0x224
[119653.427040][T730918]  binder_ioctl_write_read+0x28c/0x590
[119653.427046][T730918]  binder_ioctl+0x1b0/0xf00
[119653.427049][T730918]  __arm64_sys_ioctl+0x184/0x210
[119653.427052][T730918]  invoke_syscall+0x60/0x150
[119653.427055][T730918]  el0_svc_common+0x8c/0xf8
[119653.427057][T730918]  do_el0_svc+0x28/0xa0
[119653.427059][T730918]  el0_svc+0x24/0x84
[119653.427061][T730918]  el0t_64_sync_handler+0x88/0xec
[119653.427064][T730918]  el0t_64_sync+0x1b4/0x1b8
[119653.427067][T730918] Code: a9044ff4 d503201f 71016c3f 54000d42 
(f9470808)
[119653.427069][T730918] ---[ end trace a3882cb531ca3dd0 ]---


Reported-by: Mukesh Ojha <quic_mojha@quicinc.com>

I will try to test this patch.

Thanks,
--Mukesh

> v2: Use helper function instead of inserted code block at kfree_rcu_monitor().
> 
> Fixes: c014efeef76a ("rcu: Add multiple in-flight batches of kfree_rcu() work")
> Signed-off-by: Ziwei Dai <ziwei.dai@unisoc.com>
> ---
>   kernel/rcu/tree.c | 27 +++++++++++++++++++--------
>   1 file changed, 19 insertions(+), 8 deletions(-)
> 
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 8e880c0..7b95ee9 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -3024,6 +3024,18 @@ static void kfree_rcu_work(struct work_struct *work)
>   	return !!READ_ONCE(krcp->head);
>   }
>   
> +static bool
> +need_wait_for_krwp_work(struct kfree_rcu_cpu_work *krwp)
> +{
> +	int i;
> +
> +	for (i = 0; i < FREE_N_CHANNELS; i++)
> +		if (!list_empty(&krwp->bulk_head_free[i]))
> +			return true;
> +
> +	return !!krwp->head_free;
> +}
> +
>   static int krc_count(struct kfree_rcu_cpu *krcp)
>   {
>   	int sum = atomic_read(&krcp->head_count);
> @@ -3107,15 +3119,14 @@ static void kfree_rcu_monitor(struct work_struct *work)
>   	for (i = 0; i < KFREE_N_BATCHES; i++) {
>   		struct kfree_rcu_cpu_work *krwp = &(krcp->krw_arr[i]);
>   
> -		// Try to detach bulk_head or head and attach it over any
> -		// available corresponding free channel. It can be that
> -		// a previous RCU batch is in progress, it means that
> -		// immediately to queue another one is not possible so
> -		// in that case the monitor work is rearmed.
> -		if ((!list_empty(&krcp->bulk_head[0]) && list_empty(&krwp->bulk_head_free[0])) ||
> -			(!list_empty(&krcp->bulk_head[1]) && list_empty(&krwp->bulk_head_free[1])) ||
> -				(READ_ONCE(krcp->head) && !krwp->head_free)) {
> +		// Try to detach bulk_head or head and attach it, only when
> +		// all channels are free.  Any channel is not free means at krwp
> +		// there is on-going rcu work to handle krwp's free business.
> +		if (need_wait_for_krwp_work(krwp))
> +			continue;
>   
> +		// kvfree_rcu_drain_ready() might handle this krcp, if so give up.
> +		if (need_offload_krc(krcp)) {
>   			// Channel 1 corresponds to the SLAB-pointer bulk path.
>   			// Channel 2 corresponds to vmalloc-pointer bulk path.
>   			for (j = 0; j < FREE_N_CHANNELS; j++) {

  parent reply	other threads:[~2023-04-03 14:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 12:42 [PATCH V2] rcu: Make sure new krcp free business is handled after the wanted rcu grace period Ziwei Dai
2023-03-31 15:01 ` Uladzislau Rezki
2023-04-03  7:28   ` Uladzislau Rezki
2023-04-03 14:01 ` Mukesh Ojha [this message]
2023-04-03 22:58 ` Paul E. McKenney
2023-04-04  2:49   ` 答复: " 代子为 (Ziwei Dai)
2023-04-04  3:23     ` Paul E. McKenney
2023-04-05 17:39 ` Joel Fernandes
2023-04-05 18:12   ` Joel Fernandes
2023-04-05 18:46     ` Paul E. McKenney
2023-04-06  1:38       ` 答复: " 代子为 (Ziwei Dai)
2023-04-06  3:46         ` Paul E. McKenney
2023-04-06  4:44           ` Uladzislau Rezki
2023-04-06 14:13             ` Paul E. McKenney

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=eaf6dd0c-3402-56bd-8b58-9275b5025032@quicinc.com \
    --to=quic_mojha@quicinc.com \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=ke.wang@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=quic_neeraju@quicinc.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuang.wang@unisoc.com \
    --cc=urezki@gmail.com \
    --cc=xuewen.yan@unisoc.com \
    --cc=yifan.xin@unisoc.com \
    --cc=zhaoyang.huang@unisoc.com \
    --cc=zhiguo.niu@unisoc.com \
    --cc=ziwei.dai@unisoc.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).