public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Okash Khawaja <okash.khawaja@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: [patch 1/6] tty_port: allow a port to be opened with a tty that has no file handle
Date: Wed, 17 May 2017 14:38:32 +0100	[thread overview]
Message-ID: <20170517133832.GA463@sanghar> (raw)
In-Reply-To: <20170517074546.uzb6prh7aaa3g5ls@var.youpi.perso.aquilenet.fr>

On Wed, May 17, 2017 at 09:45:46AM +0200, Samuel Thibault wrote:
> > This issue with opening tty from userspace while it's in use from kernel. Wonder
> > if this will rear its ugly head with rescpect to the recent patches?
> 
> Ah, yes, we will have to think about that issue.

Would you suggest me raising this with Alan Cox as he mentioned some
locking to prevent this scenario?

Thanks,
Okash

  reply	other threads:[~ UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 [patch 0/6] staging: speakup: Introduce TTY-based comms Okash Khawaja
 ` [patch 1/6] tty_port: allow a port to be opened with a tty that has no file handle Okash Khawaja
     [not found]   ` <20170225192358.GA4499@sanghar>
     ` [patch 3/6] staging: speakup: refactor spk_stop_serial_interrupt Okash Khawaja
       ` [patch 4/6] staging: speakup: Add spk_ttyio Okash Khawaja
         ` [patch 5/6] staging: speakup: Make speakup_dummy use ttyio Okash Khawaja
           ` [patch 6/6] staging: speakup: Migrate acntsa, bns, dectlk and txprt to ttyio Okash Khawaja
             ` Samuel Thibault
             ` Samuel Thibault
               ` Samuel Thibault
                 ` Samuel Thibault
                   ` Okash Khawaja
                     ` Samuel Thibault
                       ` Okash Khawaja
                 ` Okash Khawaja
                   ` Samuel Thibault
                     ` Okash Khawaja
                       ` Samuel Thibault
             ` Samuel Thibault
             ` Samuel Thibault
               ` Okash Khawaja
                 ` Samuel Thibault
                   ` Okash Khawaja
                     ` Samuel Thibault
             ` Samuel Thibault
             ` Samuel Thibault
         ` [patch 4/6] staging: speakup: Add spk_ttyio Samuel Thibault
         ` Samuel Thibault
       ` [patch 3/6] staging: speakup: refactor spk_stop_serial_interrupt Samuel Thibault
         ` Okash Khawaja
           ` Samuel Thibault
     ` [patch 2/6] staging: speakup: Add serial_out method Samuel Thibault
     ` Samuel Thibault
       ` Okash Khawaja
         ` Samuel Thibault
   ` [patch 1/6] tty_port: allow a port to be opened with a tty that has no file handle Samuel Thibault
     ` Samuel Thibault
       ` John Covici
         ` Samuel Thibault
       ` Okash Khawaja
         ` Samuel Thibault
           ` Okash Khawaja [this message]
             ` Samuel Thibault
               ` Okash Khawaja
                 ` Samuel Thibault
                   ` Okash Khawaja
 ` [patch 0/6] staging: speakup: Introduce TTY-based comms Trevor Astrope
   ` Okash Khawaja
 ` Samuel Thibault
   ` Samuel Thibault
 ` Samuel Thibault
 ` Read this first :) " Samuel Thibault
   ` Okash Khawaja
     ` Samuel Thibault

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=20170517133832.GA463@sanghar \
    --to=okash.khawaja@gmail.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).