Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4766819ybi; Tue, 28 May 2019 02:06:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqwU5JIneYrRJGsBTtr5TUltGsezjMEnLbpXZLHQJ4WoB0QeOdK97zqcBR4LY2q41iyjPqL3 X-Received: by 2002:a62:53:: with SMTP id 80mr115179644pfa.183.1559034390400; Tue, 28 May 2019 02:06:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559034390; cv=none; d=google.com; s=arc-20160816; b=GR4B945Ygsel1I6pNSFO8FCxAqnUgln9mGMAF/9JGo7FEOqbyP98qtIOEd6ZteP5eH +CeW20kSIBuTEect+3jJCBqgp85q3GU41TvRP16comZGpHVWlJ8jOFs2QBh4EX1JBckD v1sIvGRkbhUNEsBjiO3T1j4aAge5w8+u7+3Fkhz/SHAA1ALfCliC/empIGqwzBcpWh5v HZYz9a8vbpItFA2zUDCdD7LfwsPlYfATe2k+SaNJ/hU9Ry0U3w6jm8k9bXUb/pgCZwLG 0/Ce+t+qed8p8AhpF3F3gHQNf35CikMr/nAOTsZIhm1m27o1eKc2M08ySSkviO3SyYqF 0i7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=DzlOvTHyKR8X8+iBqAU0JNunUmi7G22ipv63hi4doZE=; b=rTlLj9L6Ofpr7SwT30ZoLESs97G0UEhNyIsAtQ4njOo1Koen6diqyajL1BpLGvicSI 9cBTWJBfsVg2YB1H14USdftSB4cRoOw8EhOd3/qoxd7QObzxqnmGsN64LJ4D5TXLgUWN cntpY5CD+riUihe+eB4NUGnd8MojL8Xjwwm/GDpBHjLq5x8NMdmjQGGZZ1Z0qtLHqWeO b+hUfdLXs9NLnn7VsJdG4/HxxbPZEcFaa+0YJF5vFzNyVeeNUw8+5o4RjT1RXwVyqZaN OoOLPnORll6nYVJUw7+Yv5WasmakarSD0198VOR6tSewAAmZFBuIHVOgX/0rEc5oIU7j ibBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b="Ot/iReF0"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f15si21177334pgu.218.2019.05.28.02.06.12; Tue, 28 May 2019 02:06:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b="Ot/iReF0"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727235AbfE1JDw (ORCPT + 99 others); Tue, 28 May 2019 05:03:52 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:34622 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727198AbfE1JDu (ORCPT ); Tue, 28 May 2019 05:03:50 -0400 Received: by mail-ed1-f68.google.com with SMTP id p27so30688153eda.1 for ; Tue, 28 May 2019 02:03:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=DzlOvTHyKR8X8+iBqAU0JNunUmi7G22ipv63hi4doZE=; b=Ot/iReF0+zGL2ux5khVmaDK70Uagz7In4B2rbxJXjuNP8F6SbXFIAjSqOfAdZolZb2 Y/CAyNTVeJp3rkNo2d/NWhBV91roYEwu0xRWSDB8Tr7Uh5l7hmQ2p8f0CK2uPx6NBg4H dEd9pUT5bwd3PM1mf54qS2N1sUJMXiZ1VAf6s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=DzlOvTHyKR8X8+iBqAU0JNunUmi7G22ipv63hi4doZE=; b=NXvsvoJIPg4Md+tCLJ3sbwA1N4c9aEzI+lZyPdXXxgledHL9iIQOZ9yqmdY9pgR5ti gAreQppwnFvVc9AyMTNfKZyvuS1j1hsvBgQfck4wTBeMOt1k5e15hPGI+6atn3D63G16 l5jxNsvp1qOgnYrc+aeYXHdPfw0H4G8dIyngn4gFPmmGwrC+tN7nR3JgJHbmd+IaaygB IUThPJtvsnq/SkhjLHrzfQTTqjKaO/DgD3Ydax3lDLZLTjCwNzLnHDAI4fLQelYc0WlB 5bLBNjI9rJYgqdnVTjlYkm2QEuP9l3rDvLJU5UOvEClkLdxBgj2tTfDKOo25oeOiWRDH jkSQ== X-Gm-Message-State: APjAAAXrs2qbce/Q5vAkTnLLgXHsr3TVwjdSmzNEyzU9gSEoo8WmtdeE EOW4pFwuzwjfEGy91xNIsRdVYuVtYZk= X-Received: by 2002:a50:a5f1:: with SMTP id b46mr126780110edc.167.1559034227646; Tue, 28 May 2019 02:03:47 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:569e:0:3106:d637:d723:e855]) by smtp.gmail.com with ESMTPSA id x49sm4072656edm.25.2019.05.28.02.03.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 May 2019 02:03:47 -0700 (PDT) From: Daniel Vetter To: LKML Cc: DRI Development , Intel Graphics Development , linux-fbdev@vger.kernel.org, Daniel Thompson , Bartlomiej Zolnierkiewicz , Daniel Vetter , Daniel Vetter , Sam Ravnborg , Maarten Lankhorst , =?UTF-8?q?Micha=C5=82=20Miros=C5=82aw?= , Peter Rosin , Hans de Goede , Mikulas Patocka , Rob Clark Subject: [PATCH 25/33] fbmem: pull fbcon_fb_blanked out of fb_blank Date: Tue, 28 May 2019 11:02:56 +0200 Message-Id: <20190528090304.9388-26-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190528090304.9388-1-daniel.vetter@ffwll.ch> References: <20190528090304.9388-1-daniel.vetter@ffwll.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There's a callchain of: fbcon_fb_blanked -> do_(un)blank_screen -> consw->con_blank -> fbcon_blank -> fb_blank Things don't go horribly wrong because the BKL console_lock safes the day, but that's about it. And the seeming recursion is broken in 2 ways: - Starting from the fbdev ioctl we set FBINFO_MISC_USEREVENT, which tells the fbcon_blank code to not call fb_blank. This was required to not deadlock when recursing on the fb_notifier_chain mutex. - Starting from the con_blank hook we're getting saved by the console_blanked checks in do_blank/unblank_screen. Or at least that's my theory. Anyway, recursion isn't awesome, so let's stop it. Breaking the recursion avoids the need to be in the FBINFO_MISC_USEREVENT critical section, so lets move it out of that too. The astute reader will notice that fb_blank seems to require lock_fb_info(), which the fbcon code seems to ignore. I have no idea how to fix that problem, so let's keep ignoring it. v2: I forgot the sysfs blanking code. v3: Fix typo in callchain in the commmit message (Sam). Signed-off-by: Daniel Vetter Reviewed-by: Sam Ravnborg Reviewed-by: Maarten Lankhorst Cc: Sam Ravnborg Cc: Daniel Vetter Cc: Bartlomiej Zolnierkiewicz Cc: "Michał Mirosław" Cc: Peter Rosin Cc: Hans de Goede Cc: Mikulas Patocka Cc: Rob Clark --- drivers/video/fbdev/core/fbmem.c | 4 +++- drivers/video/fbdev/core/fbsysfs.c | 8 ++++++-- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c index 9366fbe99a58..d6713dce9e31 100644 --- a/drivers/video/fbdev/core/fbmem.c +++ b/drivers/video/fbdev/core/fbmem.c @@ -1068,7 +1068,6 @@ fb_blank(struct fb_info *info, int blank) event.data = ␣ early_ret = fb_notifier_call_chain(FB_EARLY_EVENT_BLANK, &event); - fbcon_fb_blanked(info, blank); if (info->fbops->fb_blank) ret = info->fbops->fb_blank(blank, info); @@ -1198,6 +1197,9 @@ static long do_fb_ioctl(struct fb_info *info, unsigned int cmd, info->flags |= FBINFO_MISC_USEREVENT; ret = fb_blank(info, arg); info->flags &= ~FBINFO_MISC_USEREVENT; + + /* might again call into fb_blank */ + fbcon_fb_blanked(info, arg); unlock_fb_info(info); console_unlock(); break; diff --git a/drivers/video/fbdev/core/fbsysfs.c b/drivers/video/fbdev/core/fbsysfs.c index 5f329278e55f..252d4f52d2a5 100644 --- a/drivers/video/fbdev/core/fbsysfs.c +++ b/drivers/video/fbdev/core/fbsysfs.c @@ -18,6 +18,7 @@ #include #include #include +#include #include #include @@ -305,12 +306,15 @@ static ssize_t store_blank(struct device *device, { struct fb_info *fb_info = dev_get_drvdata(device); char *last = NULL; - int err; + int err, arg; + arg = simple_strtoul(buf, &last, 0); console_lock(); fb_info->flags |= FBINFO_MISC_USEREVENT; - err = fb_blank(fb_info, simple_strtoul(buf, &last, 0)); + err = fb_blank(fb_info, arg); fb_info->flags &= ~FBINFO_MISC_USEREVENT; + /* might again call into fb_blank */ + fbcon_fb_blanked(fb_info, arg); console_unlock(); if (err < 0) return err; -- 2.20.1