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]
Date:	Wed, 27 Apr 2011 14:17:36 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Tomas Carnecky <tom@...ervice.com>
Cc:	Bandan Das <bandan.das@...atus.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [Bugme-new] [Bug 33842] New: NULL pointer dereference in
 ip_fragment

Le mercredi 27 avril 2011 à 13:52 +0200, Tomas Carnecky a écrit :
> On 4/27/11 9:41 AM, Eric Dumazet wrote:
> > netconsole=4444@....168.20.108/eth0,4444@....168.20.112/00:1e:0b:ec:c3:e4
> I'm not having any luck with the netconsole. The last message I see on 
> the target host is "Freeing unused kernel memory: 100k freed". I don't 
> see any messages after that. Do I need to configure the same IP address 
> in netconsole as is later configured by userspace? I set netconsole to 
> use 192.168.0.50 while the init scripts set br0 to have 192.168.0.82. 
> And would netconsole even work, as the bug is in the networking code itself?
> 
> 

It should work yes, even for a bug in networking stack.

Yes, you should take the source address you're supposed to have once
machine running. I suspect it could work with another IP address, but
using the normal one makes sure you dont hit some anti spoofing rule in
your LAN.

To check if netconsole works (after boot), you can try

dmesg -n 8
modprobe pktgen

You should see on remote machine :
pktgen: Packet Generator for packet performance testing. Version: 2.74



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ