All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majczak <lma@semihalf.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Guenter Roeck <groeck@chromium.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	upstream@semihalf.com, stable@vger.kernel.org
Subject: Re: [PATCH] serial: core: fix broken console after suspend
Date: Wed, 1 Mar 2023 10:51:31 +0100	[thread overview]
Message-ID: <CAFJ_xbp+qD-_MGd3+SgBY=8zruZNy7k3CO3OMMmWhMGhA-tARQ@mail.gmail.com> (raw)
In-Reply-To: <Y/8PUdEwskXuWZHA@kroah.com>

śr., 1 mar 2023 o 09:39 Greg Kroah-Hartman
<gregkh@linuxfoundation.org> napisał(a):
>
> On Wed, Mar 01, 2023 at 08:57:51AM +0100, Lukasz Majczak wrote:
> > Re-enable the console device after suspending, causes its cflags,
> > ispeed and ospeed to be set anew, basing on the values stored in
> > uport->cons. The issue is that these values are set only once,
> > when parsing console parameters after boot (see uart_set_options()),
> > next after configuring a port in uart_port_startup() these parameteres
> > (cflags, ispeed and ospeed) are copied to termios structure and
> > the orginal one (stored in uport->cons) are cleared, but there is no place
> > in code where those fields are checked against 0.
> > When kernel calls uart_resume_port() and setups console, it copies cflags,
> > ispeed and ospeed values from uart->cons,but those are alread cleared.
> > The efect is that console is broken.
> > This patch address this by preserving the cflags, ispeed and
> > ospeed fields in uart->cons during uart_port_startup().
> >
> > Signed-off-by: Lukasz Majczak <lma@semihalf.com>
> > Cc: stable@vger.kernel.org
> > ---
> >  drivers/tty/serial/serial_core.c | 3 ---
> >  1 file changed, 3 deletions(-)
> >
> > diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> > index 2bd32c8ece39..394a05c09d87 100644
> > --- a/drivers/tty/serial/serial_core.c
> > +++ b/drivers/tty/serial/serial_core.c
> > @@ -225,9 +225,6 @@ static int uart_port_startup(struct tty_struct *tty, struct uart_state *state,
> >                       tty->termios.c_cflag = uport->cons->cflag;
> >                       tty->termios.c_ispeed = uport->cons->ispeed;
> >                       tty->termios.c_ospeed = uport->cons->ospeed;
> > -                     uport->cons->cflag = 0;
> > -                     uport->cons->ispeed = 0;
> > -                     uport->cons->ospeed = 0;
> >               }
> >               /*
> >                * Initialise the hardware port settings.
> > --
> > 2.39.2.722.g9855ee24e9-goog
> >
>
> What commit id does this fix?
>
> thanks,
>
> greg k-h
Hi Greg,

There are actually two commits that introduce problematic uport flags
clearing in uart_startup (for the sake of simplicity I'd ignore the
older history):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.2&id=c7d7abff40c27f82fe78b1091ab3fad69b2546f9
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.2&id=027b57170bf8bb6999a28e4a5f3d78bf1db0f90c
It's 10 years between those 2 and to me it was hard to decide about
picking a proper one for the `Fixes:` tag.
How would you recommend to proceed wrt applying this patch on the
stable releases?

Best regards,
Lukasz

  reply	other threads:[~2023-03-01  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  7:57 [PATCH] serial: core: fix broken console after suspend Lukasz Majczak
2023-03-01  8:39 ` Greg Kroah-Hartman
2023-03-01  9:51   ` Lukasz Majczak [this message]
2023-03-01 12:22     ` Greg Kroah-Hartman
2023-03-01 14:09       ` Lukasz Majczak
2023-03-02 16:43         ` Lukasz Majczak
2023-03-01 11:33 ` Ilpo Järvinen

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='CAFJ_xbp+qD-_MGd3+SgBY=8zruZNy7k3CO3OMMmWhMGhA-tARQ@mail.gmail.com' \
    --to=lma@semihalf.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=upstream@semihalf.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.