linux-kernel - Re: 2.6.19-rc2-mm2

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]

Message-Id: <200610201854.43893.m.kozlowski@tuxland.pl>
Date:	Fri, 20 Oct 2006 18:54:43 +0200
From:	Mariusz Kozlowski <m.kozlowski@...land.pl>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc2-mm2

Hello, 

> Don't know.   Nothing has changed in the git-pcmcia tree since July.
>
> Are you able to bisect it, as per
> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt ?
>
> > When running without debug options enabled also these were seen amongst
> > dmesg lines:
> >
> > [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > [drm:drm_unlock] *ERROR* Process 5131 using kernel context 0
>
> <googles>
>
> This? http://lkml.org/lkml/2005/9/10/78

I think I found the culprit. It's CONFIG_PCI_MULTITHREAD_PROBE option. It is 
actually marked as EXPERIMENTAL and there is even a proper warning included 
on the help page. Disabling it makes the kernel behave the right way. So 
should what I reported be considered a real error or not? Then the next 
question is should I report errors caused by options marked as EXPERIMENTAL 
or just leave it the way it is until the option is not EXPERIMENTAL anymore?

>> This time it _is_ -mm ;-)
>> 
>Well... that's what it's for ;)  Thanks for testing.

No problem. Thanks for Linux.

Regards,

	Mariusz Kozlowski
-
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/