Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751662AbeAQCYQ (ORCPT + 1 other); Tue, 16 Jan 2018 21:24:16 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:38469 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750796AbeAQCYO (ORCPT ); Tue, 16 Jan 2018 21:24:14 -0500 X-Google-Smtp-Source: ACJfBouSfrqfAQvRQf+5lz+1fbahlrmeBSyu8Yhuxg29eE0wbCsCizSKFZYm5i/1ZJ/z7KxxLlrwAA== Date: Wed, 17 Jan 2018 11:24:09 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Sergey Senozhatsky , Steven Rostedt , Tetsuo Handa , Sergey Senozhatsky , Tejun Heo , akpm@linux-foundation.org, linux-mm@kvack.org, Cong Wang , Dave Hansen , Johannes Weiner , Mel Gorman , Michal Hocko , Vlastimil Babka , Peter Zijlstra , Linus Torvalds , Jan Kara , Mathieu Desnoyers , rostedt@home.goodmis.org, Byungchul Park , Pavel Machek , linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup Message-ID: <20180117022409.GB423@jagdpanzerIV> References: <20180112025612.GB6419@jagdpanzerIV> <20180111222140.7fd89d52@gandalf.local.home> <20180112100544.GA441@jagdpanzerIV> <20180112072123.33bb567d@gandalf.local.home> <20180113072834.GA1701@tigerII.localdomain> <20180115070637.1915ac20@gandalf.local.home> <20180115144530.pej3k3xmkybjr6zb@pathway.suse.cz> <20180116022349.GD6607@jagdpanzerIV> <20180116044716.GE6607@jagdpanzerIV> <20180116101903.iuzgln2agdr46jfy@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180116101903.iuzgln2agdr46jfy@pathway.suse.cz> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On (01/16/18 11:19), Petr Mladek wrote: [..] > > [1] https://marc.info/?l=linux-mm&m=145692016122716 > > Fixes: 6b97a20d3a79 ("printk: set may_schedule for some of console_trylock() callers") > > Signed-off-by: Sergey Senozhatsky > > Reported-by: Tetsuo Handa > > IMHO, this is a step in the right direction. > > Reviewed-by: Petr Mladek > > I'll wait for Steven's review and push this into printk.git. > I'll also add your Acks for the other patches. > > Thanks for the patch and the various observations. thanks! a side note, our console output is still largely preemptible. a typical system acquires console_sem via console_lock() all the time, so we still can have "where is my printk output?" cases. for instance, my IDLE PREEMPT x86 box, has the following stats uptime 15 min # of console_lock() calls: 10981 // can sleep under console_sem # of vprintk_emit() calls: 825 // cannot sleep under console_sem -ss