linux-kernel - Re: Assistance debugging a Micrel network driver

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

Message-ID: <p73ejju4r06.fsf@bingen.suse.de>
Date:	29 Jun 2007 19:20:09 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Greg Huber <ghuber@...teon.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Assistance debugging a Micrel network driver

Greg Huber <ghuber@...teon.com> writes:
> 
> The upper layers obviously work so I'm sure it's something in my driver.

netstat -s output might give some clue. Most packet drop
points have a counter.

> 
> I have turned on as much debugging in the kernel as I could find, but
> I get no messages. Could someone please let me know if
> there is additional debugging I should consider or if there is a
> dynamic way to turn on debugging in L2 and/or L3.

The usual is to just add printks to the kernel source code until you
find where the packet is dropped.

Or perhaps check in __kfree_skb if the skb is coming from your
driver and force a backtrace with show_stack().

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