From: "Mikko C." <mikko.cal@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, zdenek.kabelac@gmail.com,
christoph.thielecke@gmx.de, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk, grant.wilson@zen.co.uk
Subject: Re: [PATCH 2/3] inotify: do not BUG on idr entries at inotify destruction
Date: Tue, 25 Aug 2009 13:42:34 +0200 [thread overview]
Message-ID: <4A93CE2A.90509@gmail.com> (raw)
In-Reply-To: <1251146166.25096.22.camel@dhcp231-106.rdu.redhat.com>
>> On Mon, 24 Aug 2009, Eric Paris wrote:
>>>
>>> You suspect correctly. :( I'll fix in my tree before I request a
>>> pull....
I just got this with -rc7, but it doesn't look related to what I was
having before:
BUG: Bad page map in process kio_thumbnail pte:ffff88006cc99128
pmd:6d3b1067
addr:00007f9d4e3a5000 vm_flags:08000070 anon_vma:(null)
mapping:ffff88007abe21a0 index:200
vma->vm_ops->fault: filemap_fault+0x0/0x460
vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x80
Pid: 28022, comm: kio_thumbnail Not tainted 2.6.31-rc7 #1
Call Trace:
[<ffffffff810afaf4>] ? print_bad_pte+0x1d4/0x2c0
[<ffffffff810afc79>] ? vm_normal_page+0x99/0xa0
[<ffffffff810b0c7d>] ? unmap_vmas+0x4cd/0x970
[<ffffffff810b6c74>] ? exit_mmap+0x104/0x1d0
[<ffffffff81043e0d>] ? mmput+0x4d/0x100
[<ffffffff81048d81>] ? exit_mm+0x101/0x150
[<ffffffff8104b240>] ? do_exit+0x6c0/0x750
[<ffffffff8104b326>] ? do_group_exit+0x56/0xd0
[<ffffffff8104b3c2>] ? sys_exit_group+0x22/0x40
[<ffffffff8100b7eb>] ? system_call_fastpath+0x16/0x1b
Disabling lock debugging due to kernel taint
No lockups or anything.
next prev parent reply other threads:[~2009-08-25 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 17:37 [PATCH 0/3] Inotify cleanup and idr race Eric Paris
2009-08-24 17:38 ` [PATCH 1/3] inotify: seperate new watch creation updating existing watches Eric Paris
2009-08-24 17:38 ` [PATCH 2/3] inotify: do not BUG on idr entries at inotify destruction Eric Paris
2009-08-24 18:34 ` Frans Pop
2009-08-24 19:09 ` Eric Paris
2009-08-24 19:23 ` Linus Torvalds
2009-08-24 19:32 ` Eric Paris
2009-08-24 20:36 ` Eric Paris
2009-08-25 11:42 ` Mikko C. [this message]
2009-08-25 14:18 ` Eric Paris
2009-08-25 16:43 ` Linus Torvalds
2009-08-25 17:17 ` Mikko C.
2009-08-24 17:38 ` [PATCH 3/3] inotify: fix locking around inotify watching in the idr Eric Paris
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=4A93CE2A.90509@gmail.com \
--to=mikko.cal@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christoph.thielecke@gmx.de \
--cc=elendil@planet.nl \
--cc=eparis@redhat.com \
--cc=grant.wilson@zen.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zdenek.kabelac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.