mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin Winchester" <kjwinchester@gmail.com>
To: "Dave Airlie" <airlied@linux.ie>
Cc: dri-devel@lists.sourceforge.net,
	"Andi Kleen" <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/1] Convert drivers in drivers/char/drm to use .unlocked_ioctl
Date: Wed, 9 Jan 2008 08:28:53 -0400	[thread overview]
Message-ID: <d1af83620801090428nd4de198ja2adbdaab48a8ead@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.82.0801090336000.9570@skynet.skynet.ie>

On Jan 8, 2008 11:37 PM, Dave Airlie <airlied@linux.ie> wrote:
>
> > The drm drivers in this patch all used drm_ioctl to perform their
> > ioctl calls.  The common function is converted to use lock_kernel()
> > and unlock_kernel() and the drivers are converted to use .unlocked_ioctl
> >
>
> NAK
>
> I've started looking at this already in the drm git tree, I'm going to
> provide both locked and unlocked paths for drivers to choose, as we need
> to audit the drivers on a per-driver basis, the other option is to provide
> wrappers in each driver to do the lock/unlock kernel and leave drm_ioctl
> alone..
>
> I'll take a look kmalloc failure case sounds like a bug though..
>

No problem.  I interpreted Andi's request for patches as a way to ensure
that people were actively working to remove the BKL from ioctl calls.
Since you appear to already have been working towards that end, the patch
is not really necessary.

-- 
Kevin Winchester

      parent reply	other threads:[~2008-01-09 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080109005416.039551758@gmail.com>
2008-01-09  0:54 ` Kevin Winchester
2008-01-09  3:37   ` Dave Airlie
2008-01-09  4:11     ` Andi Kleen
2008-01-09  4:51       ` Dave Airlie
2008-01-09 12:28     ` Kevin Winchester [this message]

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=d1af83620801090428nd4de198ja2adbdaab48a8ead@mail.gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=airlied@linux.ie \
    --cc=andi@firstfloor.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®