linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH fix for 4.19] fbcon: Do not takeover the console from atomic context
Date: Thu, 09 Aug 2018 11:28:25 +0000	[thread overview]
Message-ID: <1e8d458b-98c1-57e8-da77-4f17eecd7360@redhat.com> (raw)
In-Reply-To: <1667652.5c9CXM81DN@amdc3058>

Hi,

On 09-08-18 12:03, Bartlomiej Zolnierkiewicz wrote:
> On Monday, August 06, 2018 05:54:16 PM Hans de Goede wrote:
>> Taking over the console involves allocating mem with GFP_KERNEL, talking
>> to drm drivers, etc. So this should not be done from an atomic context.
>>
>> But the console-output trigger deferred console takeover may happen from an
>> atomic context, which leads to "BUG: sleeping function called from invalid
>> context" errors.
>>
>> This commit fixes these errors by doing the deferred takeover from a
>> workqueue when the notifier runs from an atomic context.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> 
> checkpatch.pl complains about in_atomic use:
> 
> ERROR: do not use in_atomic in drivers
> #51: FILE: drivers/video/fbdev/core/fbcon.c:3623:
> +       if (in_atomic() || irqs_disabled()) {
> 
> please also see the comment in preempt.h:
> 
> /*
>   * Are we running in atomic context?  WARNING: this macro cannot
>   * always detect atomic context; in particular, it cannot know about
>   * held spinlocks in non-preemptible kernels.  Thus it should not be
>   * used in the general case to determine whether sleeping is possible.
>   * Do not use in_atomic() in driver code.
>   */
> #define in_atomic()	(preempt_count() != 0)
> 
> Therefore please explain why it is fine to use in_atomic in fbcon's case.

Ok I will send a v2 which adds a comment why we need to use in_atomic
here.

Regards,

Hans


> 
>> ---
>>   drivers/video/fbdev/core/fbcon.c | 21 +++++++++++++++++++--
>>   1 file changed, 19 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbcon.c
>> index ef8b2d0b7071..4e5997d53fc4 100644
>> --- a/drivers/video/fbdev/core/fbcon.c
>> +++ b/drivers/video/fbdev/core/fbcon.c
>> @@ -3592,7 +3592,20 @@ static int fbcon_init_device(void)
>>   }
>>   
>>   #ifdef CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER
>> +static void fbcon_register_existing_fbs(struct work_struct *work)
>> +{
>> +	int i;
>> +
>> +	console_lock();
>> +
>> +	for_each_registered_fb(i)
>> +		fbcon_fb_registered(registered_fb[i]);
>> +
>> +	console_unlock();
>> +}
>> +
>>   static struct notifier_block fbcon_output_nb;
>> +static DECLARE_WORK(fbcon_deferred_takeover_work, fbcon_register_existing_fbs);
>>   
>>   static int fbcon_output_notifier(struct notifier_block *nb,
>>   				 unsigned long action, void *data)
>> @@ -3607,8 +3620,12 @@ static int fbcon_output_notifier(struct notifier_block *nb,
>>   	deferred_takeover = false;
>>   	logo_shown = FBCON_LOGO_DONTSHOW;
>>   
>> -	for_each_registered_fb(i)
>> -		fbcon_fb_registered(registered_fb[i]);
>> +	if (in_atomic() || irqs_disabled()) {
>> +		schedule_work(&fbcon_deferred_takeover_work);
>> +	} else {
>> +		for_each_registered_fb(i)
>> +			fbcon_fb_registered(registered_fb[i]);
>> +	}
>>   
>>   	return NOTIFY_OK;
>>   }
> 
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
> 

      reply	other threads:[~2018-08-09 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180806155422epcas2p137fabf6869ce6217c0f34266f19f978c@epcas2p1.samsung.com>
2018-08-06 15:54 ` [PATCH fix for 4.19] fbcon: Do not takeover the console from atomic context Hans de Goede
2018-08-09 10:03   ` Bartlomiej Zolnierkiewicz
2018-08-09 11:28     ` Hans de Goede [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e8d458b-98c1-57e8-da77-4f17eecd7360@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).