mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrea Righi <righi.andrea@gmail.com>,
	Dave Jones <davej@redhat.com>, Dave Airlie <airlied@redhat.com>
Subject: Re: lockdep splat from ioctl and mmap fops sharing lock
Date: Sat, 25 Oct 2008 11:12:26 +0200	[thread overview]
Message-ID: <4902E2FA.10209@s5r6.in-berlin.de> (raw)
In-Reply-To: <8763njjmqt.fsf@saeurebad.de>

Johannes Weiner wrote:
> Stefan Richter <stefanr@s5r6.in-berlin.de> writes:
> 
>> Johannes Weiner wrote:
>>> raw1394_ioctl() doing usercopy under fi->state_mutex
>>> raw1394_mmap() taking fi->state_mutex under mmap_sem
...
>> was the usage of mmap_sem changed after 2.6.27 or were my tests
>> insufficient?
> 
> In linux-next/-mm, copy_to/from_user have lockdep annotations telling
> that they might fault and therefor acquire the mmap_sem in #PF.
> 
> But since faults on ioctl parameters are so rare, without these
> annotations you would probably never see a warning.

Thanks for the report and explanation.  I logged this as 
http://bugzilla.kernel.org/show_bug.cgi?id=11823 (dv1394, won't fix) and 
http://bugzilla.kernel.org/show_bug.cgi?id=11824 (raw1394, to be fixed 
in the 2.6.28-rc timeframe since it is a post 2.6.27 regression).
-- 
Stefan Richter
-=====-==--- =-=- ==--=
http://arcgraph.de/sr/

  reply	other threads:[~2008-10-25  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23  3:23 lockdep splat from fbmem Johannes Weiner
2008-10-23 13:10 ` Andrea Righi
2008-10-23 13:58 ` lockdep splat from ioctl and mmap fops sharing lock Johannes Weiner
2008-10-23 15:08   ` Stefan Richter
2008-10-23 16:32     ` Johannes Weiner
2008-10-25  9:12       ` Stefan Richter [this message]
2008-10-28 22:33 ` lockdep splat from fbmem Andrea Righi

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=4902E2FA.10209@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=airlied@redhat.com \
    --cc=davej@redhat.com \
    --cc=hannes@saeurebad.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=righi.andrea@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

Powered by JetHome