From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH v3 4/4] printk: Drop console_sem during panic
Date: Fri, 04 Feb 2022 10:53:48 -0800 [thread overview]
Message-ID: <87v8xuea4j.fsf@stepbren-lnx.us.oracle.com> (raw)
In-Reply-To: <Yfyl2TSdFmn7HqmV@google.com>
Sergey Senozhatsky <senozhatsky@chromium.org> writes:
> On (22/02/01 10:58), Stephen Brennan wrote:
>> +/*
>> + * Return true when this CPU should unlock console_sem without pushing all
>> + * messages to the console. This reduces the chance that the console is
>> + * locked when the panic CPU tries to use it.
>> + */
>> +static bool abandon_console_lock_in_panic(void)
>> +{
>> + if (!panic_in_progress())
>> + return false;
>> +
>> + /*
>> + * We can use raw_smp_processor_id() here because it is impossible for
>> + * the task to be migrated to the panic_cpu, or away from it. If
>> + * panic_cpu has already been set, and we're not currently executing on
>> + * that CPU, then we never will be.
>> + */
>> + return atomic_read(&panic_cpu) != raw_smp_processor_id();
>> +}
>> +
>> /*
>> * Can we actually use the console at this time on this cpu?
>> *
>> @@ -2746,6 +2765,10 @@ void console_unlock(void)
>> if (handover)
>> return;
>>
>> + /* Allow panic_cpu to take over the consoles safely */
>> + if (abandon_console_lock_in_panic())
>> + break;
>
> Sorry, why not just `return` like in handover case?
We need to drop console_sem before returning, since the whole benefit
here is to increase the chance that console_sem is unlocked when the
panic_cpu halts this CPU.
in the handover case, there's another cpu waiting, and we're essentially
transferring the console_sem ownership to that cpu, so we explicitly
return and skip the unlocking portion.
Does this need some comments to clarify it?
Admittedly if I had a few more lines of context in the diff, you would
see the console unlock directly after the loop; it's a bit clearer when
you're looking at the function as whole:
2768 /* Allow panic_cpu to take over the consoles safely */
2769 if (abandon_console_lock_in_panic())
2770 break;
2771
2772 if (do_cond_resched)
2773 cond_resched();
2774 }
2775
2776 /* Get consistent value of the next-to-be-used sequence number. */
2777 next_seq = console_seq;
2778
2779 console_locked = 0;
2780 up_console_sem();
Stephen
>
>> +
>> if (do_cond_resched)
>> cond_resched();
>> }
>> @@ -2763,7 +2786,7 @@ void console_unlock(void)
>> * flush, no worries.
>> */
>> retry = prb_read_valid(prb, next_seq, NULL);
>> - if (retry && console_trylock())
>> + if (retry && !abandon_console_lock_in_panic() && console_trylock())
>> goto again;
>> }
>> EXPORT_SYMBOL(console_unlock);
next prev parent reply other threads:[~2022-02-04 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 18:57 [PATCH v3 0/4] printk: reduce deadlocks " Stephen Brennan
2022-02-01 18:57 ` [PATCH v3 1/4] printk: Add panic_in_progress helper Stephen Brennan
2022-02-02 1:39 ` Stephen Brennan
2022-02-01 18:58 ` [PATCH v3 2/4] printk: disable optimistic spin during panic Stephen Brennan
2022-02-01 18:58 ` [PATCH v3 3/4] printk: Avoid livelock with heavy printk " Stephen Brennan
2022-02-01 18:58 ` [PATCH v3 4/4] printk: Drop console_sem " Stephen Brennan
2022-02-04 4:04 ` Sergey Senozhatsky
2022-02-04 18:53 ` Stephen Brennan [this message]
2022-02-08 2:15 ` Sergey Senozhatsky
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=87v8xuea4j.fsf@stepbren-lnx.us.oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
Powered by JetHome