From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org
Cc: Marc Zyngier <maz@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Guenter Roeck <linux@roeck-us.net>,
Anatoly Pugachev <matorola@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v1] serial: core: Initialise spin lock before use in uart_configure_port()
Date: Mon, 6 Jul 2020 17:36:30 +0300 [thread overview]
Message-ID: <20200706143630.GX3703480@smile.fi.intel.com> (raw)
In-Reply-To: <20200706140036.75524-1-andriy.shevchenko@linux.intel.com>
On Mon, Jul 06, 2020 at 05:00:36PM +0300, Andy Shevchenko wrote:
> The comment near to uart_port_spin_lock_init() says:
>
> Ensure that the serial console lock is initialised early.
> If this port is a console, then the spinlock is already initialised.
>
> and there is nothing about enabled or disabled consoles. The commit
> a3cb39d258ef ("serial: core: Allow detach and attach serial device
> for console") made a change, which follows the comment, and also to
> prevent reinitialisation of the lock in use, when user detaches and
> attaches back the same console device. But this change discovers
> another issue, that uart_add_one_port() tries to access a spin lock
> that now may be uninitialised. This happens when a driver expects
> the serial core to register a console on its behalf. In this case
> we must initialise a spin lock before use.
Abandon this version, please, I forgot to squash it with the typo fix.
v2 has been sent.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-07-06 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 14:00 [PATCH v1] serial: core: Initialise spin lock before use in uart_configure_port() Andy Shevchenko
2020-07-06 14:36 ` Andy Shevchenko [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=20200706143630.GX3703480@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matorola@gmail.com \
--cc=maz@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox