Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751613AbdF0EyW (ORCPT ); Tue, 27 Jun 2017 00:54:22 -0400 Received: from mail1.bemta12.messagelabs.com ([216.82.251.9]:62603 "EHLO mail1.bemta12.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751483AbdF0EyI (ORCPT ); Tue, 27 Jun 2017 00:54:08 -0400 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRWlGSWpSXmKPExsWS8eIhk+7bJ4G RBhvahCzWvLnFYnF51xw2i9MTe5gt9nU8YLL4sLSXyeLm+qVsDmweHz7GebTsu8XusWvbTiaP d+fOsXt83iQXwBrFmpmXlF+RwJrxuvsPW8FDqYozE28zNTBukepi5OIQEnjCKHHq3DNmCGcBo 8SerTdZuxg5OdgEdCSmn9jFBmKLCGRI9Dy/DlbELHCYUeJWcxs7iCMs0MUo0fvmPRuIIyLQzS ix8kE/M0SLk8TRs9tZQGwWAVWJ7Ut+ARVxcPAK+Eh07vGCWLeaUWLr1otMIDWcAjYSUw9PAVv HKCArMe3RfbA4s4C4xNxps8BOkhAQkFiy5zwzhC0q8fLxP1aQmRIC8hJbZgmCmMwCmhLrd+lD dCpKTOl+yA5i8woISpyc+YRlAqPILCRDZyF0zELSMQtJxwJGllWMGsWpRWWpRbpG5npJRZnpG SW5iZk5uoaGRnq5qcXFiempOYlJxXrJ+bmbGIHxVs/AwLiDcVOj1yFGSQ4mJVFeoaWBkUJ8Sf kplRmJxRnxRaU5qcWHGGU4OJQkeNWA8SskWJSanlqRlpkDjHyYtAQHj5IIb9lxoDRvcUFibnF mOkTqFKOilDhvMEifAEgiozQPrg2WbC4xykoJ8zIyMDAI8RSkFuVmlqDKv2IU52BUEuaNB5nC k5lXAjf9FdBiJqDFLPMCQBaXJCKkpBoYnyf9Fs2RTNewjOBXe5ViH/bmk4qC4+K2xEIl81Q+T 2nbqBtTiv9sz5zradWQ/0x7x+KTQlcKE2Z67fUzjLHpNRGscjoXbR/bPUM/b/a/TM+8U6EXpM 5zmpw58vSY8f4KjiMFB6/PMg0QNAo69+3992U6Fcn+q8rfFIfWSTx7E/xebNrC/otKLMUZiYZ azEXFiQCxasEyMQMAAA== X-Env-Sender: liufeng24@lenovo.com X-Msg-Ref: server-12.tower-168.messagelabs.com!1498539243!65467025!1 X-Originating-IP: [104.232.225.2] X-StarScan-Received: X-StarScan-Version: 9.4.19; banners=-,-,- X-VirusChecked: Checked From: Feng Feng24 Liu To: Sebastian Andrzej Siewior , "Steven Rostedt" CC: Mike Galbraith , "linux-kernel@vger.kernel.org" , "linux-rt-users@vger.kernel.org" , "tmac@hp.com" Subject: RE: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027 Thread-Topic: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027 Thread-Index: AdLuQ56eUD35kh7GScSpVqAQXpco4QAAThoAAAEO5wAALgahQA== Date: Tue, 27 Jun 2017 04:53:33 +0000 Message-ID: <2B18E8E1DDAE074A82D1060396451DAE263CC1AE@CNMAILEX04.lenovo.com> References: <2B18E8E1DDAE074A82D1060396451DAE263CBBD6@CNMAILEX04.lenovo.com> <20170626102418.310bb1ce@gandalf.local.home> <20170626145436.npgsaz4eyvnh2j2k@linutronix.de> In-Reply-To: <20170626145436.npgsaz4eyvnh2j2k@linutronix.de> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.96.19.89] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v5R4sbj7004077 Content-Length: 2474 Lines: 59 Hi, Sebastian I just add the RT patches, nothing else. Thanks Feng >-----Original Message----- >From: Sebastian Andrzej Siewior [mailto:sebastian.siewior@linutronix.de] >Sent: Monday, June 26, 2017 10:55 PM >To: Steven Rostedt >Cc: Feng Feng24 Liu; Mike Galbraith; linux-kernel@vger.kernel.org; >linux-rt-users@vger.kernel.org; tmac@hp.com >Subject: Re: BUG: unable to handle kernel NULL pointer dereference at >0000000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027 > >On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote: >> > CPU: 17 PID: 1738811 Comm: ip Not tainted 4.4.70-thinkcloud-nfv #1 >> > Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01GR174, BIOS >> > -[TCE124M-2.10]- 06/23/2016 >> > task: ffff881cda2c27c0 ti: ffff881ea0538000 task.ti: >> > ffff881ea0538000 >> > RIP: 0010:[] [] >> > __try_to_take_rt_mutex+0x34/0x160 >> > RSP: 0018:ffff881ea053bb50 EFLAGS: 00010082 >> > RAX: 0000000000000000 RBX: ffff881f805416a8 RCX: 0000000000000000 >> > RDX: ffff881ea053bb98 RSI: ffff881cda2c27c0 RDI: ffff881f805416a8 >> > RBP: ffff881ea053bb60 R08: 0000000000000001 R09: 0000000000000002 >> > R10: 0000000000000a01 R11: 0000000000000001 R12: ffff881cda2c27c0 >> > R13: ffff881cda2c27c0 R14: 0000000000000202 R15: ffff881f6b0c27c0 >> > FS: 00007f28be315740(0000) GS:ffff88205f8c0000(0000) >> > knlGS:0000000000000000 >> > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> > CR2: 0000000000000038 CR3: 0000001e9e479000 CR4: 00000000003406e0 >> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 >> > Stack: >> > ffff881f805416a8 ffff881ea053bb98 ffff881ea053bc28 ffffffff81a8f03d >> > ffff881ea053c000 01ff881ea053bb90 ffff881cda2c27c0 ffff881f6b0c27c1 >> > ffff881cda2c2eb0 0000000000000001 0000000000000000 >> > 0000000000000000 Call Trace: >> > [] rt_spin_lock_slowlock+0x13d/0x390 >> > [] rt_spin_lock+0x1f/0x30 >> > [] lockref_get_not_dead+0xf/0x50 >> > [] ns_get_path+0x61/0x1d0 >> >> Hmm, this is in the filesystem code. What were you doing when this >> happened? > >and do you have any patches except the RT patch? > >> >> > <4>Jun 24 10:01:19 node-1 kernel: [44959.446268] >> > [] proc_ns_follow_link+0x89/0xa0 >> >> Do you know what proc file it was reading? >> >> -- Steve > >Sebastian