From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Okash Khawaja <okash.khawaja@gmail.com>
Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Jiri Slaby <jslaby@suse.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org, William Hubbs <w.d.hubbs@gmail.com>,
Chris Brannon <chris@the-brannons.com>,
Kirk Reiser <kirk@reisers.ca>,
speakup@linux-speakup.org, devel@driverdev.osuosl.org
Subject: Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
Date: Mon, 17 Jul 2017 14:31:45 +0200 [thread overview]
Message-ID: <20170717123145.GE24503@kroah.com> (raw)
In-Reply-To: <20170713112954.GA665@sanghar>
On Thu, Jul 13, 2017 at 12:29:54PM +0100, Okash Khawaja wrote:
> On Wed, Jul 12, 2017 at 07:20:28PM +0100, Alan Cox wrote:
> >
> > > When opening from kernel, we don't use file pointer. The count mismatch
> > > is between tty->count and #fd's. So opening from kernel leads to #fd's
> > > being less than tty->count. I thought this difference is relevant to
> > > user-space opening of tty, and not to kernel opening of tty. Can you
> > > suggest how to address this mismatch?
> >
> > Your kernel reference is the same as having a file open reference so I
> > think this actually needs addressing in the maths. In other words count
> > the number of kernel references and also add that into the test for
> > check_tty_count (kernel references + #fds == count).
> >
> > I'd really like to keep this right because that check has a long history
> > of catching really nasty race conditions in the tty code. The
> > open/close/hangup code is really fragile so worth the debugability.
>
> I see. Okay based this, check_tty_count can be easily updated to take
> into account kernel references.
Ok, I'll drop this series from my "to-apply" queue and wait for you to
redo it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-17 12:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 20:28 tty contention resulting from tty_open_by_device export Okash Khawaja
2017-07-08 8:38 ` Greg Kroah-Hartman
2017-07-08 9:01 ` Okash Khawaja
2017-07-09 11:41 ` [patch 0/3] " Okash Khawaja
2017-07-09 11:41 ` [patch 1/3] tty: resolve tty contention between kernel and user space Okash Khawaja
2017-07-09 11:51 ` Greg Kroah-Hartman
2017-07-09 15:04 ` Andy Shevchenko
2017-07-09 19:08 ` Okash Khawaja
2017-07-10 8:31 ` Okash Khawaja
2017-07-10 15:21 ` Andy Shevchenko
2017-07-10 16:12 ` Okash Khawaja
2017-07-09 11:41 ` [patch 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver Okash Khawaja
2017-07-09 11:50 ` Greg Kroah-Hartman
2017-07-09 12:28 ` Okash Khawaja
2017-07-09 11:41 ` [patch 3/3] tty: undo export " Okash Khawaja
2017-07-09 11:57 ` [patch 0/3] Re: tty contention resulting from tty_open_by_device export Greg Kroah-Hartman
2017-07-09 12:32 ` [patch 4/3] tty: make tty_kopen return ENODEV in case of no TTY Okash Khawaja
2017-07-10 11:52 ` [patch 0/3] Re: tty contention resulting from tty_open_by_device export Alan Cox
2017-07-10 12:33 ` Okash Khawaja
2017-07-10 16:22 ` Okash Khawaja
2017-07-12 18:20 ` Alan Cox
2017-07-13 11:29 ` Okash Khawaja
2017-07-17 12:31 ` Greg Kroah-Hartman [this message]
2017-07-17 13:23 ` Okash Khawaja
2017-07-17 22:04 ` Alan Cox
2017-07-18 11:29 ` Okash Khawaja
2017-07-18 12:26 ` Dan Carpenter
2017-07-18 19:22 ` Okash Khawaja
2017-07-18 13:49 ` Alan Cox
2017-07-20 7:22 ` [patch v3 0/3] tty contention resulting from tty_open_by_driver export Okash Khawaja
2017-07-20 7:22 ` [patch v3 1/3] tty: resolve tty contention between kernel and user space Okash Khawaja
2017-07-20 7:22 ` [patch v3 2/3] staging: speakup: use tty_kopen and tty_kclose Okash Khawaja
2017-07-20 7:22 ` [patch v3 3/3] tty: undo export of tty_open_by_driver Okash Khawaja
2017-07-17 21:04 ` [patch v2 0/3] tty contention resulting from tty_open_by_driver export Okash Khawaja
2017-07-17 21:04 ` [patch v2 1/3] tty: resolve tty contention between kernel and user space Okash Khawaja
2017-07-17 21:04 ` [patch v2 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver Okash Khawaja
2017-07-17 21:04 ` [patch v2 3/3] tty: undo export " Okash Khawaja
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=20170717123145.GE24503@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jslaby@suse.com \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=okash.khawaja@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@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 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.