From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161891AbcEaHzt (ORCPT ); Tue, 31 May 2016 03:55:49 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34747 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755416AbcEaHzs (ORCPT ); Tue, 31 May 2016 03:55:48 -0400 Date: Tue, 31 May 2016 09:55:45 +0200 From: Michal Hocko To: kernel test robot Cc: lkp@01.org, LKML , 0day robot Subject: Re: [mm, oom_adj] 9954f89181: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ] Message-ID: <20160531075545.GF26128@dhcp22.suse.cz> References: <574c9c97.F/FfSVgxrdCJGrju%xiaolong.ye@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <574c9c97.F/FfSVgxrdCJGrju%xiaolong.ye@intel.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 31-05-16 04:03:35, kernel test robot wrote: > > > FYI, we noticed the following commit: > > https://github.com/0day-ci/linux Michal-Hocko/Handle-oom-bypass-more-gracefully/20160530-210927 > commit 9954f891814d3f23e10036d2b6404cc80aaa461b ("mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj") JFTR this patch the underlying code has changed and sighand lock has been removed. See the current state in attempts/process-share-mm-oom-sanitization branch at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git > (md-udevd)/256 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: > (md-udevd)/256 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: > ( (&(&p->alloc_lock)->rlock&(&p->alloc_lock)->rlock){+.+...}){+.+...}, at: , at: [] find_lock_task_mm+0x98/0x1b0 > [] find_lock_task_mm+0x98/0x1b0 -- Michal Hocko SUSE Labs