LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] tty add compat_ioctl
Date: Thu, 03 May 2007 21:05:25 -0600 [thread overview]
Message-ID: <463AA2F5.7030307@microgate.com> (raw)
In-Reply-To: <463A8FF9.3080607@microgate.com>
Paul Fulghum wrote:
> Arnd Bergmann wrote:
>> - In your driver you don't get the big kernel lock in the
>> compat_ioctl function. I assume that this is correct for
>> the particular driver, but it may be nice if you could
>> consequently also add an unlocked_ioctl function that can
>> be used without the BKL for native ioctls. It would be good
>> to hear an opinon on this from someone who has an insight
>> in tty locking issues though, so I'm Cc:ing some people
>> who have touched that recently.
>
> I don't count on higher level locking for
> synchronization issues specific to the driver.
>
> I thought the current compat_ioctl() was already
> meant to *not* have the BKL just like unlocked_ioctl.
> My thought was that any driver getting a recent update
> like compat_ioctl() would need to be reviewed for BKL
> safety and take the lock manually if necessary.
Nevermind. I misread what you wrote (I'm tired).
Yes, adding an unlocked_ioctl() makes sense.
--
Paul
next prev parent reply other threads:[~2007-05-04 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 17:34 Paul Fulghum
[not found] ` <200705040223.46326.arnd@arndb.de>
2007-05-04 1:44 ` Paul Fulghum
2007-05-04 3:05 ` Paul Fulghum [this message]
2007-05-04 21:11 ` Paul Fulghum
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=463AA2F5.7030307@microgate.com \
--to=paulkf@microgate.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] tty add compat_ioctl' \
/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
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).