linux-kernel - Re: 2.6.22 Oops attaching usb-storage device

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>] [day] [month] [year] [list]

Message-ID: <20070711153215.GU22103@vianova.fi>
Date:	Wed, 11 Jul 2007 18:32:15 +0300
From:	Ville Herva <v@....fi>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22 Oops attaching usb-storage device

On Wed, Jul 11, 2007 at 04:17:14PM +0200, you [Michal Piotrowski] wrote:
> Hi,
> 
> On 11/07/07, Ville Herva <v@....fi> wrote:
> >[98790.366620] Modules linked in: ub nvidia(P) ppp_deflate zlib_deflate 
>
> "When you are using a binary driver, the kernel is "tainted", which
> means that the source of possible problems may be unrelated to the
> kernel code (see
> https://secure-support.novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html
> for more details). You can check whether or not the kernel was tainted
> when the problem occurred by looking at the corresponding error
> message. If can you see something similar to the following line:
> EIP:      0060:[<c046c7c3>]         Tainted: P      VLI
> (the word Tainted is crucial here), the kernel was tainted and most
> probably the kernel developers will not be able to help you. In that
> case you should try to reproduce the problem without the binary driver
> loaded. Moreover, if the problem does not occur without it, you should
> send a bug report to the creators of the binary driver and ask them to
> ???x it."

Thanks, I do know the kernel was tainted (Nvidia display driver). 

I didn't explicitly mention that in the report, since the kernel developers
see that from the oops message, and because I believe there is a fair change
that the hated nvidia module played no role in this case. Of course, there's
no way to be sure, as it is closed source.

I sent the oops message just in case the usb-storage / usb people can get an
idea from the stack trace what might have gone wrong. I believe it was worth
it even though nvidia module might in theory make the problem unsolvable. 

The problem is spurious (not reproducible). I attached and removed the Nokia
device quite some times today and yesterday without problems, and this only
happened once. 

As regards to nvidia being able to fix this problem, I sure you understand
that will not happen :) Even if it was the nvidia driver mucking arounf the
kernel address space, that would have to be very random and this oops
message couldn't help them.

-- v -- 

v@....fi

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