All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Safonov <dima@arista.com>
To: Guilherme Piccoli <gpiccoli@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 3/7] tty: Hold tty_ldisc_lock() during tty_reopen()
Date: Fri, 12 Oct 2018 16:57:37 +0100	[thread overview]
Message-ID: <1539359857.2706.23.camel@arista.com> (raw)
In-Reply-To: <CAHD1Q_xv4PSsJ3AcKd5i+QZ8On9jqPZsa+p46bCiKubhzVJerQ@mail.gmail.com>

Hi Guilherme,

Just to let you know - I've done with more urgent issues now,
so I'll be back on this patch on Monday, installing qemu-system-hppa
and debugging the root case.

Thanks,
Dmitry

On Wed, 2018-10-03 at 07:46 -0300, Guilherme Piccoli wrote:
> On Tue, Oct 2, 2018 at 6:33 PM Dmitry Safonov <dima@arista.com>
> wrote:
> > [...]
> > Well, v5 passes 0day, so all previous reports are fixed.
> > But there is a new one about reboot on parisc platform which takes
> > ~3
> > mins after the patch with ldisc locked on tty_reopen().
> > 
> > I believe it's related to holding read side for too long..
> > So, the patches still need another fix, heh.
> > 
> > Unfortunately, I was a bit busy with other bugs hitting more in
> > Arista.
> 
> Hi Dmitry, thank you! Yeah, I saw that reading the whole thread after
> sending this email heheh
> That's a bummer =/
> 
> Unfortunately, I don't have a reproducer to exercise your patch. Do
> you
> have some recipe on how to reproduce it easily?
> I'll try more, in order I can validate the reboot behavior here.
> 
> 
> > > > I'd like to ask you if you did respin the patch with Greg's
> > > > suggestion
> > > > for the tag - I couldn't find it in LKML heheh
> > > > 
> > > > Oh, if you can CC me in future spins of this patch (in case
> > > > there
> > > > any),
> > > > I'd really be glad.
> > 
> > Sure, will enlarge Cc list ;)
> > 
> 
> Thanks again!
> Cheers,
> 
> 
> Guilherme

  reply	other threads:[~2018-10-12 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8c61fd04-969a-cb09-6595-7ee23d214ab1@canonical.com>
2018-10-01 19:01 ` [PATCHv5 3/7] tty: Hold tty_ldisc_lock() during tty_reopen() Guilherme G. Piccoli
2018-10-02 21:33   ` Dmitry Safonov
2018-10-03 10:46     ` Guilherme Piccoli
2018-10-12 15:57       ` Dmitry Safonov [this message]
2018-10-15 12:16         ` Guilherme Piccoli
2018-09-17 23:52 [PATCHv5 0/7] tty: Hold write ldisc sem in tty_reopen() Dmitry Safonov
2018-09-17 23:52 ` [PATCHv5 3/7] tty: Hold tty_ldisc_lock() during tty_reopen() Dmitry Safonov
2018-09-18 13:47   ` Greg Kroah-Hartman
2018-09-18 14:19     ` Dmitry Safonov

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=1539359857.2706.23.camel@arista.com \
    --to=dima@arista.com \
    --cc=gpiccoli@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.