From: Okash Khawaja <okash.khawaja@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: 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" <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 1/3] tty: resolve tty contention between kernel and user space
Date: Mon, 10 Jul 2017 09:31:05 +0100 [thread overview]
Message-ID: <20170710083105.GA719@sanghar> (raw)
In-Reply-To: <CAHp75VdwWNj8PHRAMLqcQKhtT=sS5-n9T3n8GY1Rte=MKOQV-w@mail.gmail.com>
On Sun, Jul 09, 2017 at 06:04:17PM +0300, Andy Shevchenko wrote:
> On Sun, Jul 9, 2017 at 2:41 PM, Okash Khawaja <okash.khawaja@gmail.com> wrote:
>
> > +struct tty_struct *tty_kopen(dev_t device)
> > +{
> > + struct tty_struct *tty;
> > + struct tty_driver *driver = NULL;
> > + int index = -1;
> > +
> > + mutex_lock(&tty_mutex);
> > + driver = tty_lookup_driver(device, NULL, &index);
> > + if (IS_ERR(driver)) {
>
> > + mutex_unlock(&tty_mutex);
> > + return ERR_CAST(driver);
>
> Hmm... perhaps
>
> tty = ERR_CAST(driver);
> goto out_unlock;
>
> See below for further details.
>
Sorry missed this one out. Since tty_lookup_driver has failed, we don't
need to down the refcount on driver. So we can return here, without
going to out_unlock.
Thanks,
Okash
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
tty contention resulting from tty_open_by_device export Okash Khawaja
[not found] ` <20170708083803.GA23080@kroah.com>
` Okash Khawaja
` [patch 0/3] " Okash Khawaja
` [patch 1/3] tty: resolve tty contention between kernel and user space Okash Khawaja
[not found] ` <CAHp75VdwWNj8PHRAMLqcQKhtT=sS5-n9T3n8GY1Rte=MKOQV-w@mail.gmail.com>
` Okash Khawaja
` Okash Khawaja [this message]
[not found] ` <CAHp75VeEjExnouxPqxPg8uVBJXRiWOpLSSypeDMNTheD3aJLNg@mail.gmail.com>
` Okash Khawaja
` [patch 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver Okash Khawaja
[not found] ` <20170709115055.GA14769@kroah.com>
` Okash Khawaja
` [patch 3/3] tty: undo export " Okash Khawaja
` [patch 4/3] tty: make tty_kopen return ENODEV in case of no TTY Okash Khawaja
[not found] ` <20170710125233.2006733e@alans-desktop>
` [patch 0/3] Re: tty contention resulting from tty_open_by_device export Okash Khawaja
` Okash Khawaja
[not found] ` <20170712192028.70bc0d54@alans-desktop>
` Okash Khawaja
[not found] ` <20170717123145.GE24503@kroah.com>
` Okash Khawaja
[not found] ` <20170717230438.5c3bd397@alans-desktop>
` Okash Khawaja
[not found] ` <20170718122637.l5v3re2gcjbxkzeq@mwanda>
` Okash Khawaja
` [patch v2 0/3] tty contention resulting from tty_open_by_driver export Okash Khawaja
` [patch v2 1/3] tty: resolve tty contention between kernel and user space Okash Khawaja
` [patch v2 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver Okash Khawaja
` [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=20170710083105.GA719@sanghar \
--to=okash.khawaja@gmail.com \
--cc=andy.shevchenko@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 read-only IMAP folder(s) and NNTP newsgroup(s).