From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755123AbcBZT7o (ORCPT ); Fri, 26 Feb 2016 14:59:44 -0500 Received: from mail-pa0-f44.google.com ([209.85.220.44]:35074 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755078AbcBZT7m (ORCPT ); Fri, 26 Feb 2016 14:59:42 -0500 Subject: Re: [RFC PATCH] kernfs: create raw version kernfs_path_len and kernfs_path To: Steven Rostedt References: <1456510505-6620-1-git-send-email-yang.shi@linaro.org> <20160226135628.09ce727c@gandalf.local.home> <56D0A97E.90706@linaro.org> Cc: gregkh@linuxfoundation.org, tj@kernel.org, lizefan@huawei.com, tglx@linutronix.de, bigeasy@linutronix.de, linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, linaro-kernel@lists.linaro.org From: "Shi, Yang" Message-ID: <56D0AEAC.3070002@linaro.org> Date: Fri, 26 Feb 2016 11:59:40 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <56D0A97E.90706@linaro.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/26/2016 11:37 AM, Shi, Yang wrote: > On 2/26/2016 10:56 AM, Steven Rostedt wrote: >> On Fri, 26 Feb 2016 10:15:05 -0800 >> Yang Shi wrote: >> >>> commit 5634cc2aa9aebc77bc862992e7805469dcf83dac ("writeback: update >>> writeback >>> tracepoints to report cgroup") made writeback tracepoints report cgroup >>> writeback, but it may trigger the below bug on -rt kernel since >>> kernfs_path >>> and kernfs_path_len are called by tracepoints, which acquire sleeping >>> lock. >>> >>> BUG: sleeping function called from invalid context at >>> kernel/locking/rtmutex.c:930 >>> in_atomic(): 1, irqs_disabled(): 0, pid: 625, name: kworker/u16:3 >>> INFO: lockdep is turned off. >>> Preemption disabled at:[] wb_writeback+0xec/0x830 >>> >>> CPU: 7 PID: 625 Comm: kworker/u16:3 Not tainted 4.4.1-rt5 #20 >>> Hardware name: Freescale Layerscape 2085a RDB Board (DT) >>> Workqueue: writeback wb_workfn (flush-7:0) >>> Call trace: >>> [] dump_backtrace+0x0/0x200 >>> [] show_stack+0x24/0x30 >>> [] dump_stack+0x88/0xa8 >>> [] ___might_sleep+0x2ec/0x300 >>> [] rt_spin_lock+0x38/0xb8 >>> [] kernfs_path_len+0x30/0x90 >>> [] >>> trace_event_raw_event_writeback_work_class+0xe8/0x2e8 >>> [] wb_writeback+0x620/0x830 >>> [] wb_workfn+0x61c/0x950 >>> [] process_one_work+0x3ac/0xb30 >>> [] worker_thread+0x9c/0x7a8 >>> [] kthread+0x190/0x1b0 >>> [] ret_from_fork+0x10/0x30 >>> >>> Since kernfs_* functions are heavily used by cgroup, so it sounds not >>> reasonable to convert kernfs_rename_lock to raw lock. >>> >>> Create raw version kernfs_path, kernfs_path_len and cgroup_path, >>> which don't >>> acquire lock and are used by tracepoints only. >>> >> >> And what prevents name from being freed while the tracepoint is reading >> it? >> >> Perhaps we need this change as well: > > Thanks for pointing this out. Yes, it looks we need this since the > tracepoints are protected by rcu_read_lock_sched. > > Will add this in V2. BTW, it sounds this is not the only point where kernfs_node could be updated, __kernfs_remove should need synchronize_sched too. Thanks, Yang > > Yang > >> >> -- Steve >> >> diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c >> index 996b7742c90b..d2ef153145c0 100644 >> --- a/fs/kernfs/dir.c >> +++ b/fs/kernfs/dir.c >> @@ -1397,6 +1397,12 @@ int kernfs_rename_ns(struct kernfs_node *kn, >> struct kernfs_node *new_parent, >> kn->hash = kernfs_name_hash(kn->name, kn->ns); >> kernfs_link_sibling(kn); >> >> + /* >> + * Tracepoints may be reading the old name. They are protected >> + * by rcu_read_lock_sched(). >> + */ >> + synchronize_sched(); >> + >> kernfs_put(old_parent); >> kfree_const(old_name); >> >> >