From: Greg KH <gregkh@linuxfoundation.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: 4.12 mainline crash in n_tty_receive_buf_common when using g_serial
Date: Wed, 8 Jan 2020 14:43:36 +0100 [thread overview]
Message-ID: <20200108134336.GA2377543@kroah.com> (raw)
In-Reply-To: <CAAfyv35wRyoZMjep=DPOGNk_gX-GxoKknmU1Gu97dUvcUaAEgw@mail.gmail.com>
On Wed, Jan 08, 2020 at 01:38:08PM +0100, Belisko Marek wrote:
> Hi Greg,
>
> On Wed, Jan 8, 2020 at 1:25 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Jan 08, 2020 at 12:49:52PM +0100, Belisko Marek wrote:
> > > Hi,
> > >
> > > we're using mainline 4.12 kernel (bit too old I know) on am335x board.
> >
> > That's _MUCH_ too old and obsolete and broken, there's nothing the
> > community can do about this, sorry. Please update to a modern kernel
> > version, like 5.4, and we will be glad to help.
> Yes I know it's old but it's behaving fine just hit this issue
> recently. Will take a look if we can bump to something latest.
> >
> > If you are stuck at 4.12 due to a SoC vendor issue, please contact that
> > vendor for support as you are already paying for it from them.
> No it' no vendor kernel it's really mainline (from yocto build).
Then there really is no reason to be using such an old and totally
insecure kernel version. That's almost a liability :)
thanks,
greg k-h
prev parent reply other threads:[~2020-01-08 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 11:49 4.12 mainline crash in n_tty_receive_buf_common when using g_serial Belisko Marek
2020-01-08 12:25 ` Greg KH
2020-01-08 12:38 ` Belisko Marek
2020-01-08 13:43 ` Greg KH [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=20200108134336.GA2377543@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=marek.belisko@gmail.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).