From: Mikulas Patocka <mpatocka@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniel Axtens <dja@axtens.net>,
Michael Neuling <mikey@neuling.org>,
Peter Hurley <peter@hurleysoftware.com>,
Jiri Slaby <jslaby@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tty crash in Linux 4.6
Date: Tue, 27 Mar 2018 08:18:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1803270818150.30055@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <20180322140554.GA3273@kroah.com>
On Thu, 22 Mar 2018, Greg Kroah-Hartman wrote:
> On Fri, Mar 23, 2018 at 12:48:06AM +1100, Daniel Axtens wrote:
> > Hi,
> >
> > >> This patch works, I've had no tty crashes since applying it.
> > >>
> > >> I've seen that you haven't sent this patch yet to Linux-4.7-rc and
> > >> Linux-4.6-stable. Will you? Or did you create a different patch?
> > >
> > > We are hitting this now on powerpc. This patch never seemed to make
> > > it upstream (drivers/tty/tty_ldisc.c hasn't been touched in 1 year).
> >
> > I seem to be hitting this too on a kernel that has the 4.6 changes
> > backported to 4.4.
> >
> > Has there been any further progress on getting this accepted?
>
> Can you try applying 28b0f8a6962a ("tty: make n_tty_read() always abort
> if hangup is in progress") to see if that helps out or not?
>
> thanks,
>
> greg k-h
It doesn't help. I get the same crash as before.
Mikulas
next prev parent reply other threads:[~2018-03-27 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 20:12 tty crash in Linux 4.6 Mikulas Patocka
2016-05-16 23:36 ` Peter Hurley
2016-05-17 15:57 ` Peter Hurley
2016-05-17 18:09 ` Peter Hurley
2016-05-17 21:26 ` Mikulas Patocka
2016-07-07 22:57 ` Mikulas Patocka
2017-03-11 0:31 ` Michael Neuling
2018-03-22 13:48 ` Daniel Axtens
2018-03-22 14:05 ` Greg Kroah-Hartman
2018-03-27 12:18 ` Mikulas Patocka [this message]
2018-04-11 16:09 ` Daniel Axtens
2019-11-15 19:21 ` Mike Kravetz
2019-11-16 9:36 ` Greg Kroah-Hartman
2019-12-03 15:17 ` Mikulas Patocka
2019-12-03 19:14 ` Greg Kroah-Hartman
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=alpine.LRH.2.02.1803270818150.30055@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=dja@axtens.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=peter@hurleysoftware.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.