linux-kernel - Re: [PATCH 2/3] inotify: do not BUG on idr entries at inotify destruction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Aug 2009 10:18:24 -0400
From:	Eric Paris <eparis@...hat.com>
To:	"Mikko C." <mikko.cal@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	zdenek.kabelac@...il.com, christoph.thielecke@....de,
	akpm@...ux-foundation.org, viro@...iv.linux.org.uk,
	grant.wilson@....co.uk
Subject: Re: [PATCH 2/3] inotify: do not BUG on idr entries at inotify
 destruction

On Tue, 2009-08-25 at 13:42 +0200, Mikko C. wrote:
> >> 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.

I can safely say that I have absolutely no idea, but I'm doubting it is
mine.

Does everyone who hit the: kernel BUG at fs/notify/notification.c:93!
have CONFIG_DEBUG_VM=N ?   Mikko indicated that his problems seem to
crop up with CONFIG_DEBUG_VM=N but not when he enabled it.  I'll be
testing again today with it disabled.....

-Eric


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/