linux-kernel - Re: [BUG] Linux 2.6.20.1 - unable to handle kernel paging request

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, 1 Mar 2007 13:27:49 +0000 (GMT)
From:	Chris Rankin <rankincj@...oo.com>
To:	Pekka J Enberg <penberg@...helsinki.fi>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] Linux 2.6.20.1 - unable to handle kernel paging request - accessing freed memory?

Oh yes - I'd better mention what my Ethernet devices are:

$ cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo
colls carrier compressed
    lo:  820705   15570    0    0    0     0          0         0   820705   15570    0    0    0 
   0       0          0
  eth0: 3289077   14258    0    0    0     0          0       639  1379700   14175    0    0    0 
   0       0          0
  eth1:       0       0    0    0    0     0          0         0        0  0    0    0    0     0
      0          0
  eth2:       0       0    0    0    0     0          0         0        0  0    0    0    0     0
      0          0


$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0D:56:0D:E7:3F
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20d:56ff:fe0d:e73f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14262 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14175 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3289533 (3.1 MiB)  TX bytes:1379700 (1.3 MiB)
          Base address:0xdcc0 Memory:ff6e0000-ff700000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:15570 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15570 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:820705 (801.4 KiB)  TX bytes:820705 (801.4 KiB)

# /sbin/ifconfig eth1
eth1      Link encap:UNSPEC  HWaddr 87-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

# /sbin/ifconfig eth2
eth2      Link encap:UNSPEC  HWaddr 00-02-3C-00-A1-03-71-11-00-00-00-00-00-00-00-00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

I think that eth1 and eth2 are both "eth1394" devices, automatically loaded on the two Firewire
"hubs"(?) in this machine?

Cheers,
Chris



		
___________________________________________________________ 
All New Yahoo! Mail  Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
-
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/