From: Okash Khawaja <okash.khawaja@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Cc: 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: [patch v3 0/3] tty contention resulting from tty_open_by_driver export
Date: Thu, 20 Jul 2017 08:22:35 +0100 [thread overview]
Message-ID: <20170720072235.186761910@gmail.com> (raw)
In-Reply-To: <20170718144931.0f6c9634@alans-desktop>
Hi,
I have updated the patches so that the exclusivity flag is in tty_port.
When closing the struct - by calling tty_release_struct - we also need
to reset the flag. One way to do that is to reset the flag inside
tty_release_struct function, regardless of whether the tty was opened
through tty_kopen or not. In order to keep the code clean, I have
instead created a separate function called tty_kclose which is the same
as tty_release_struct except that it also resets the exclusivity flag.
As a result, any changes to tty_release_struct won't be in tty_kclose
untless manually added. Please advise on this.
Here is a summary of changes when compared to v2:
- Patch 1 uses TTY_PORT_KOPENED flag instead of TTY_KOPENED and as a
result adds helper functions to read and change the flag
- Patch 1 adds tty_kclose function to close tty opened by tty_kopen
- Patch 2 calls tty_kclose instead of tty_release_struct
Thanks,
Okash
next prev parent reply other threads:[~2017-07-20 7:29 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
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 ` Okash Khawaja [this message]
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=20170720072235.186761910@gmail.com \
--to=okash.khawaja@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--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 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).