From: James Hogan <jhogan@kernel.org>
To: stable@vger.kernel.org
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
linux-mips@linux-mips.org, linux-serial@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Nicolas Schichan <nschichan@freebox.fr>
Subject: Re: [PATCH RFC 3/3] MIPS: AR7: ensure the port type's FCR value is used
Date: Mon, 22 Jan 2018 13:07:19 +0000 [thread overview]
Message-ID: <20180122130718.GA22211@saruman> (raw)
In-Reply-To: <20171029152721.6770-4-jonas.gorski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
Hi stable maintainers,
On Sun, Oct 29, 2017 at 04:27:21PM +0100, Jonas Gorski wrote:
> Since commit aef9a7bd9b67 ("serial/uart/8250: Add tunable RX interrupt
> trigger I/F of FIFO buffers"), the port's default FCR value isn't used
> in serial8250_do_set_termios anymore, but copied over once in
> serial8250_config_port and then modified as needed.
>
> Unfortunately, serial8250_config_port will never be called if the port
> is shared between kernel and userspace, and the port's flag doesn't have
> UPF_BOOT_AUTOCONF, which would trigger a serial8250_config_port as well.
>
> This causes garbled output from userspace:
>
> [ 5.220000] random: procd urandom read with 49 bits of entropy available
> ers
> [kee
>
> Fix this by forcing it to be configured on boot, resulting in the
> expected output:
>
> [ 5.250000] random: procd urandom read with 50 bits of entropy available
> Press the [f] key and hit [enter] to enter failsafe mode
> Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
>
> Fixes: aef9a7bd9b67 ("serial/uart/8250: Add tunable RX interrupt trigger I/F of FIFO buffers")
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
Please can this patch be applied to stable branches 3.17+. It is now
merged into mainline as commit 0a5191efe06b ("MIPS: AR7: ensure the port
type's FCR value is used").
Commit b084116f8587 ("MIPS: AR7: Ensure that serial ports are properly
set up") is a prerequisite for it to apply cleanly, but is already
tagged for stable.
Thanks
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-22 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 15:27 [PATCH 0/3] MIPS: AR7: assorted fixes Jonas Gorski
2017-10-29 15:27 ` [PATCH 1/3] MIPS: AR7: defer registration of GPIO Jonas Gorski
2017-10-29 17:33 ` Florian Fainelli
2017-10-29 15:27 ` [PATCH 2/3] MIPS: AR7: ensure that serial ports are properly set up Jonas Gorski
2017-10-29 17:33 ` Florian Fainelli
2017-10-29 15:27 ` [PATCH RFC 3/3] MIPS: AR7: ensure the port type's FCR value is used Jonas Gorski
2017-11-14 11:02 ` James Hogan
2017-12-28 15:38 ` Jonas Gorski
2018-01-02 8:40 ` James Hogan
2018-01-22 13:07 ` James Hogan [this message]
2018-01-22 13:34 ` Greg Kroah-Hartman
2017-11-08 22:03 ` [PATCH 0/3] MIPS: AR7: assorted fixes James Hogan
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=20180122130718.GA22211@saruman \
--to=jhogan@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=nschichan@freebox.fr \
--cc=ralf@linux-mips.org \
--cc=stable@vger.kernel.org \
--cc=yoshihiro.yunomae.ez@hitachi.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;
as well as URLs for NNTP newsgroup(s).