linux-kernel - Re: 2.6.25-git16 -- BUG: unable to handle kernel NULL pointer dereference at 00000000 -- IP: [<c02dd5d5>] fw_show_drv_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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 01 May 2008 10:37:21 -0400
From:	Dan Noé <dpn@...merica.net>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	krh@...hat.com, linux1394-devel@...ts.sourceforge.net
Subject: Re: 2.6.25-git16 -- BUG: unable to handle kernel NULL pointer dereference
 at 00000000 -- IP: [<c02dd5d5>] fw_show_drv_device_ids+0xd9/0xee

Stefan Richter wrote:
> I could look into keeping those messages down to only a single one per 
> attempt to fetch the so-called configuration ROM of an added node.

Seems like this is ideal.

> (The ROM CRC error warning has been added in 2.6.22.  Before Linux 
> 2.6.22, the ROM CRC errors were silently accepted.  The new alternative 
> firewire drivers also do not warn about ROM CRC errors... yet...)

I like to be warned about things, even if there isn't anything I can 
really do about it (fix my IEEE 1394 ROM CRC? :) But there doesn't seem 
to be any point to repeating the message.

Do the repeats come because it prints each time the config ROM is accessed?

Cheers,
Dan

-- 
                     /--------------- - -  -  -   -   -
                     |  Dan Noé
                     |  http://isomerica.net/~dpn/
--
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/