From: Chen Jun <chenjun102@huawei.com>
To: <stable@vger.kernel.org>, <gregkh@linuxfoundation.org>
Cc: <xuqiang36@huawei.com>
Subject: [PATCH stable 4.9 1/4] printk: Export is_console_locked
Date: Thu, 4 Aug 2022 08:14:06 +0000 [thread overview]
Message-ID: <20220804081409.121787-2-chenjun102@huawei.com> (raw)
In-Reply-To: <20220804081409.121787-1-chenjun102@huawei.com>
From: Hans de Goede <hdegoede@redhat.com>
commit d48de54a9dab5370edd2e991f78cc7996cf5483e upstream
This is a preparation patch for adding a number of WARN_CONSOLE_UNLOCKED()
calls to the fbcon code, which may be built as a module (event though
usually it is not).
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Acked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Acked-by: Petr Mladek <pmladek@suse.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Signed-off-by: Chen Jun <chenjun102@huawei.com>
---
kernel/printk/printk.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index f1f115b3ee01..c3ae4e17d69d 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2221,6 +2221,7 @@ int is_console_locked(void)
{
return console_locked;
}
+EXPORT_SYMBOL(is_console_locked);
/*
* Check if we have any console that is capable of printing while cpu is
--
2.17.1
next prev parent reply other threads:[~2022-08-04 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 8:14 [PATCH stable 4.9 0/4] Fix CVE-2021-33655 Chen Jun
2022-08-04 8:14 ` Chen Jun [this message]
2022-08-04 8:14 ` [PATCH stable 4.9 2/4] fbmem: Check virtual screen sizes in fb_set_var() Chen Jun
2022-08-04 8:14 ` [PATCH stable 4.9 3/4] fbcon: Disallow setting font bigger than screen size Chen Jun
2022-08-04 8:14 ` [PATCH stable 4.9 4/4] fbcon: Prevent that screen size is smaller than font size Chen Jun
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=20220804081409.121787-2-chenjun102@huawei.com \
--to=chenjun102@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xuqiang36@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.