slab corruption in skb allocs

slab corruption in skb allocs

[Richard Fuchs]

[-- Attachment #1: Type: text/plain, Size: 5102 bytes --]

hello all!

the memory allocation debugger gives me the following messages under a
vanilla 2.6.10 and 2.6.11 kernel when doing

1) hdparm -d0 on my hard disk
2) tar c / > /dev/null
3) sending lots of network traffic to the machine (e.g. close to 100
mbit/s udp packets)

-----------------------------------------------------
Slab corruption: start=de9141a4, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3b c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c 41 d0 40 00 40 11 33 78
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Next obj: start=de9149b0, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Slab corruption: start=de92e8b0, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3c c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c 41 cf 40 00 40 11 33 79
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Prev obj: start=de92e0a4, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=de92f0bc, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Slab corruption: start=def5e3a4, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3b c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c e3 14 40 00 40 11 92 33
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Next obj: start=def5ebb0, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Slab corruption: start=de938b30, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3c c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c e3 13 40 00 40 11 92 34
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Prev obj: start=de938324, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=de93933c, len=2048
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<c03b7e97>](alloc_skb+0x47/0xf0)
000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
010: 5a 5a 20 a0 00 00 42 cd a9 1e ff ff ff ff 3c c0
Slab corruption: start=de96aa30, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3b c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c 0d e4 40 00 40 11 67 64
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Prev obj: start=de96a224, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=de96b23c, len=2048
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<c03b7e97>](alloc_skb+0x47/0xf0)
000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
010: 5a 5a 00 00 00 00 b6 81 15 1f ff ff ff ff 00 00
Slab corruption: start=de8fa5a4, len=2048
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3c c0
020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
030: 00 df 08 00 45 00 00 1c 0d e3 40 00 40 11 67 65
040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
Next obj: start=de8fadb0, len=2048
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<c03b7e97>](alloc_skb+0x47/0xf0)
000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
010: 5a 5a 00 00 00 00 ce 96 92 1e ff ff ff ff 00 00
-----------------------------------------------------

and so on. the disk activity alone or the network traffic alone doesn't
trigger this. also doing the same with dma enabled doesn't trigger this
either, but when everything comes together i get this within a second.
kernel is not smp and preempt is not enabled.

kernel config (from 2.6.11) is attached; if you need any more info, let
me know. is this a kernel issue, or could the hardware be at fault?

cheers
richard



[-- Attachment #2: config --]
[-- Type: text/plain, Size: 22782 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11
# Thu Mar  3 18:58:39 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_HOTPLUG is not set
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PC-card bridges
#
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=y
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
CONFIG_BLK_DEV_CMD64X=y
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
CONFIG_SCSI_BUSLOGIC=y
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=y
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_INET_TUNNEL=y
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_IPRANGE=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_DSCP=y
CONFIG_IP_NF_MATCH_AH_ESP=y
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_MATCH_PHYSDEV=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_MATCH_REALM=y
CONFIG_IP_NF_MATCH_SCTP=y
CONFIG_IP_NF_MATCH_COMMENT=y
CONFIG_IP_NF_MATCH_HASHLIMIT=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_DSCP=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_CLASSIFY=y
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_BROUTE=y
CONFIG_BRIDGE_EBT_T_FILTER=y
# CONFIG_BRIDGE_EBT_T_NAT is not set
CONFIG_BRIDGE_EBT_802_3=y
CONFIG_BRIDGE_EBT_AMONG=y
CONFIG_BRIDGE_EBT_ARP=y
CONFIG_BRIDGE_EBT_IP=y
CONFIG_BRIDGE_EBT_LIMIT=y
CONFIG_BRIDGE_EBT_MARK=y
CONFIG_BRIDGE_EBT_PKTTYPE=y
CONFIG_BRIDGE_EBT_STP=y
CONFIG_BRIDGE_EBT_VLAN=y
CONFIG_BRIDGE_EBT_ARPREPLY=y
# CONFIG_BRIDGE_EBT_DNAT is not set
CONFIG_BRIDGE_EBT_MARK_T=y
CONFIG_BRIDGE_EBT_REDIRECT=y
# CONFIG_BRIDGE_EBT_SNAT is not set
CONFIG_BRIDGE_EBT_LOG=y
# CONFIG_BRIDGE_EBT_ULOG is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=y
CONFIG_VLAN_8021Q=y
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_HFSC=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_NETEM=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
# CONFIG_CLS_U32_PERF is not set
# CONFIG_NET_CLS_IND is not set
# CONFIG_CLS_U32_MARK is not set
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
CONFIG_NET_PKTGEN=y
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
CONFIG_BONDING=y
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
CONFIG_ETHERTAP=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
CONFIG_VORTEX=y
CONFIG_TYPHOON=y
CONFIG_LANCE=y
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
CONFIG_DEPCA=y
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
CONFIG_B44=y
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
CONFIG_NATSEMI=y
CONFIG_NE2K_PCI=y
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=y
CONFIG_EPIC100=y
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
CONFIG_VIA_RHINE=y
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=y
# CONFIG_R8169_NAPI is not set
CONFIG_R8169_VLAN=y
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set

#
# XFS support
#
CONFIG_XFS_FS=y
CONFIG_XFS_EXPORT=y
# CONFIG_XFS_RT is not set
CONFIG_XFS_QUOTA=y
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
CONFIG_MINIX_FS=y
CONFIG_ROMFS_FS=y
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
CONFIG_TMPFS_XATTR=y
CONFIG_TMPFS_SECURITY=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=y
CONFIG_HFS_FS=y
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
CONFIG_HPFS_FS=y
CONFIG_QNX4FS_FS=y
CONFIG_SYSV_FS=y
CONFIG_UFS_FS=y
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=y
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_AMIGA_PARTITION=y
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Hardware crypto devices
#

#
# Library routines
#
CONFIG_CRC_CCITT=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: slab corruption in skb allocs

[Andrew Morton]

Richard Fuchs <richard.fuchs@inode.info> wrote:
>
> hello all!
> 
> the memory allocation debugger gives me the following messages under a
> vanilla 2.6.10 and 2.6.11 kernel when doing
> 
> 1) hdparm -d0 on my hard disk
> 2) tar c / > /dev/null
> 3) sending lots of network traffic to the machine (e.g. close to 100
> mbit/s udp packets)
> 
> -----------------------------------------------------
> Slab corruption: start=de9141a4, len=2048
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<c03b8163>](kfree_skbmem+0x13/0x30)
> 010: 6b 6b 20 a0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 3b c0
> 020: 6b 6b 00 0b cd 1e 1f d2 00 04 23 01 c7 6f 81 00
> 030: 00 df 08 00 45 00 00 1c 41 d0 40 00 40 11 33 78
> 040: c0 a8 22 1d c0 a8 22 1b 80 52 30 18 00 08 89 ea
> 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6b 6b
> ...
> 
> and so on. the disk activity alone or the network traffic alone doesn't
> trigger this. also doing the same with dma enabled doesn't trigger this
> either, but when everything comes together i get this within a second.
> kernel is not smp and preempt is not enabled.
> 
> kernel config (from 2.6.11) is attached; if you need any more info, let
> me know. is this a kernel issue, or could the hardware be at fault?

I guess it could be hardware.  But given that disabling DMA _causes_ the
problem, rather than fixes it, it seems unlikely.

Could you enable CONFIG_DEBUG_PAGEALLOC in .config and see it that triggers
an oops?

Re: slab corruption in skb allocs

[Richard Fuchs]

Andrew Morton wrote:

> I guess it could be hardware.  But given that disabling DMA _causes_ the
> problem, rather than fixes it, it seems unlikely.
> 
> Could you enable CONFIG_DEBUG_PAGEALLOC in .config and see it that triggers
> an oops?

by now, i could reproduce this on two different machines with quite 
different hardware, while a third doesn't seem to show those symptoms. 
on the second machine, i got the corruption errors from the slab 
debugger mostly from the disk access alone, the network traffic was only 
minimal (but still present). i was doing write operations on the hdd in 
this test.

kernel 2.6.7 doesn't show this behavior, while all kernels from 2.6.9 
and up do. (i didn't test 2.6.8.x).

as for DEBUG_PAGEALLOC... when i enable this option, the errors from 
DEBUG_SLAB magically disappear. however, my ssh session got disconnected 
once while doing the disk access with the message:

Received disconnect from 195.58.172.154: 2: Bad packet length 4239103034.

never seen this before and not sure if this has anything to do with it...

cheers
richard

Re: slab corruption in skb allocs

[Dave Jones]

On Fri, Mar 04, 2005 at 10:55:31AM +0100, Richard Fuchs wrote:
 > hello all!
 > 
 > the memory allocation debugger gives me the following messages under a
 > vanilla 2.6.10 and 2.6.11 kernel when doing
 > 
 > 1) hdparm -d0 on my hard disk
 > 2) tar c / > /dev/null
 > 3) sending lots of network traffic to the machine (e.g. close to 100
 > mbit/s udp packets)

Which network drivers are in use on the box that gets the corruption ?

		Dave

Re: slab corruption in skb allocs

[Richard Fuchs]

Dave Jones wrote:

> Which network drivers are in use on the box that gets the corruption ?

all three that i tested it on are using the e100 driver. the boxes with 
pci id 8086:1039 and 8086:1229 are seeing corruptions, the one with pci 
id 8086:2449 is not.

i will try again the eepro100 driver and see if it does the same...

cheers
richard

Re: slab corruption in skb allocs

[Richard Fuchs]

Richard Fuchs wrote:

 > [e100]
> i will try again the eepro100 driver and see if it does the same...

yes, the same thing happens with the eepro100 driver.

cheers
richard

Re: slab corruption in skb allocs

[Matt Mackall]

On Fri, Mar 04, 2005 at 01:23:48PM +0100, Richard Fuchs wrote:
> Andrew Morton wrote:
> 
> >I guess it could be hardware.  But given that disabling DMA _causes_ the
> >problem, rather than fixes it, it seems unlikely.
> >
> >Could you enable CONFIG_DEBUG_PAGEALLOC in .config and see it that triggers
> >an oops?
> 
> by now, i could reproduce this on two different machines with quite 
> different hardware, while a third doesn't seem to show those symptoms. 
> on the second machine, i got the corruption errors from the slab 
> debugger mostly from the disk access alone, the network traffic was only 
> minimal (but still present). i was doing write operations on the hdd in 
> this test.
> 
> kernel 2.6.7 doesn't show this behavior, while all kernels from 2.6.9 
> and up do. (i didn't test 2.6.8.x).
> 
> as for DEBUG_PAGEALLOC... when i enable this option, the errors from 
> DEBUG_SLAB magically disappear. however, my ssh session got disconnected 
> once while doing the disk access with the message:
> 
> Received disconnect from 195.58.172.154: 2: Bad packet length 4239103034.

Send the output of ethtool, please. This tends to be checksum
offloading not working as it should or the like. Can you repeat this
with bulk ssh traffic?

-- 
Mathematics is the supreme nostalgia of our time.

Re: slab corruption in skb allocs

[Richard Fuchs]

_correction_ to my previous mail, this does _not_ happen with the 
eepro100 driver. (sorry for the confusion, i got the kernel images mixed 
up with all the testing i've been doing.)

could this affect the e1000 driver as well?


Matt Mackall wrote:

> Send the output of ethtool, please.

box 1, affected:

Settings for eth0:
         Supported ports: [ TP MII ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Supports auto-negotiation: Yes
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Advertised auto-negotiation: Yes
         Speed: 100Mb/s
         Duplex: Full
         Port: MII
         PHYAD: 1
         Transceiver: internal
         Auto-negotiation: on
         Current message level: 0x000020c1 (8385)
         Link detected: yes



box 2, affected:

         Supported ports: [ TP MII ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Supports auto-negotiation: Yes
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Advertised auto-negotiation: Yes
         Speed: 100Mb/s
         Duplex: Full
         Port: MII
         PHYAD: 1
         Transceiver: internal
         Auto-negotiation: on
         Supports Wake-on: g
         Wake-on: g
         Current message level: 0x00000007 (7)
         Link detected: yes



box 3, not affected:

         Supported ports: [ TP MII ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Supports auto-negotiation: Yes
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
         Advertised auto-negotiation: Yes
         Speed: 100Mb/s
         Duplex: Full
         Port: MII
         PHYAD: 1
         Transceiver: internal
         Auto-negotiation: on
         Supports Wake-on: g
         Wake-on: g
         Current message level: 0x00000007 (7)
         Link detected: yes


> This tends to be checksum
> offloading not working as it should or the like. Can you repeat this
> with bulk ssh traffic?

yes, with various strange effects:

Received disconnect from 195.58.172.154: 2: Bad packet length 919251405.

or

Received disconnect from 195.58.172.154: 2: Corrupted MAC on input.


cheers
richard

Re: slab corruption in skb allocs

[Matt Mackall]

On Fri, Mar 04, 2005 at 10:19:21PM +0100, Richard Fuchs wrote:
> _correction_ to my previous mail, this does _not_ happen with the 
> eepro100 driver. (sorry for the confusion, i got the kernel images mixed 
> up with all the testing i've been doing.)
> 
> could this affect the e1000 driver as well?

Yes. 

> >Send the output of ethtool, please.

Doh. 'ethtool -k' is what's needed, sorry.

If it's reproduceable, try turning off rx/tx hardware checksumming:

ethtool -k eth0 rx off tx off

-- 
Mathematics is the supreme nostalgia of our time.

Re: slab corruption in skb allocs

[Richard Fuchs]

Matt Mackall wrote:

> Doh. 'ethtool -k' is what's needed, sorry.

doh myself. :) this won't be very helpful though, as i get the same on 
all machines (with both drivers):

Offload parameters for eth0:
Cannot get device rx csum settings: Operation not supported
Cannot get device tx csum settings: Operation not supported
Cannot get device scatter-gather settings: Operation not supported
Cannot get device tcp segmentation offload settings: Operation not supported
no offload info available

> ethtool -k eth0 rx off tx off

ditto. i'll try to reproduce this on a machine with e1000 though...


cheers
richard

Re: slab corruption in skb allocs

[Matt Mackall]

On Fri, Mar 04, 2005 at 10:52:38PM +0100, Richard Fuchs wrote:
> Matt Mackall wrote:
> 
> >Doh. 'ethtool -k' is what's needed, sorry.
> 
> doh myself. :) this won't be very helpful though, as i get the same on 
> all machines (with both drivers):
> 
> Offload parameters for eth0:
> Cannot get device rx csum settings: Operation not supported
> Cannot get device tx csum settings: Operation not supported
> Cannot get device scatter-gather settings: Operation not supported
> Cannot get device tcp segmentation offload settings: Operation not supported
> no offload info available

Which card/driver is this? Is this the same card that's showing ssh
troubles? My theory about your ssh trouble only applies to cards with
checksum offload.

-- 
Mathematics is the supreme nostalgia of our time.

Re: slab corruption in skb allocs

[Richard Fuchs]

Matt Mackall wrote:

> Which card/driver is this? Is this the same card that's showing ssh
> troubles? My theory about your ssh trouble only applies to cards with
> checksum offload.

i got the same on all three machines i was testing with, with both the 
e100 and the eepro100 driver. one of those three machines was the one 
with the ssh troubles, its card is identified as "Intel Corp. 82557/8/9 
[Ethernet Pro 100] (rev 08)", pci id 8086:1229. plus, i couldn't 
reproduce those problems on a machine with e1000, which does support all 
kinds of checksum offloading. (there might still be something fishy with 
the e1000 as well, as i'm not entirely trusting the errors from the slab 
checkers alone. especially since i don't see those messages when i 
enable page alloc debugging.)

another machine behaves even more strangely... its nic is identified as 
"Intel Corp. 82801BD PRO/100 VE (LOM) Ethernet Controller (rev 81)", pci 
id 8086:1039, also apparently not supporting hardware checksums. it does 
immediately produce the slab debug errors when i bombard it with udp 
packets while having disk access w/o dma, but remains silent when doing 
the same with a tcp transfer instead of udp packets. neither ssh traffic 
nor /dev/zero piped through netcat (no matter in which direction) makes 
it catch any errors. i only got a _single_ message from the slab 
debugger when sending /dev/zero through netcat in _both_ directions at 
the same time (in and out). however, i do get pages and pages of those 
messages when sending a simple stream of udp packets to the box... 
again, this is all with the e100 driver, i couldn't produce any similar 
results with the eepro100 or the e1000 driver yet, but apparently this 
doesn't necessarily mean that there isn't something wrong anyway...

cheers
richard

Re: slab corruption in skb allocs

[Scott Feldman]

On Mar 4, 2005, at 4:23 AM, Richard Fuchs wrote:
> kernel 2.6.7 doesn't show this behavior, while all kernels from 2.6.9 
> and up do. (i didn't test 2.6.8.x).

Was NAPI turned on for e100 in 2.6.7?  If not, turn NAPI on in the 
2.6.7 driver and see if you get the same result.  If you do, it's very 
likely the bug is in the e100 driver's NAPI implementation.

-scott

Re: slab corruption in skb allocs

[Richard Fuchs]

Scott Feldman wrote:

> Was NAPI turned on for e100 in 2.6.7?  If not, turn NAPI on in the 2.6.7 
> driver and see if you get the same result.  If you do, it's very likely 
> the bug is in the e100 driver's NAPI implementation.

looks like you are right, enabling NAPI in 2.6.7 does trigger this.

what exactly is this? i didn't enable NAPI in any of the newer kernel 
versions i was trying, so i'm somewhat confused. :)  also, does this 
affect the e1000 driver in any way?

cheers
richard

Re: slab corruption in skb allocs

[Scott Feldman]

On Mar 5, 2005, at 11:10 AM, Richard Fuchs wrote:

> Scott Feldman wrote:
>
>> Was NAPI turned on for e100 in 2.6.7?  If not, turn NAPI on in the 
>> 2.6.7 driver and see if you get the same result.  If you do, it's 
>> very likely the bug is in the e100 driver's NAPI implementation.
>
> looks like you are right, enabling NAPI in 2.6.7 does trigger this.
>
> what exactly is this?

A bug in the driver.  I have a hunch: please try this patch with 2.6.9 
or higher:

http://marc.theaimsgroup.com/?l=linux-netdev&m=110726809431611&w=2

> i didn't enable NAPI in any of the newer kernel versions i was trying, 
> so i'm somewhat confused. :)

NAPI is the only option for new kernels.  2.6.7 had both NAPI and 
non-NAPI.

>   also, does this affect the e1000 driver in any way?

No.  e1000 is a totally different driver/device with very similar name.

-scott

Re: slab corruption in skb allocs

[Richard Fuchs]

Scott Feldman wrote:
> On Mar 5, 2005, at 11:10 AM, Richard Fuchs wrote:

>> looks like you are right, enabling NAPI in 2.6.7 does trigger this.
>>
>> what exactly is this?

> A bug in the driver.  I have a hunch: please try this patch with 2.6.9 
> or higher:
> 
> http://marc.theaimsgroup.com/?l=linux-netdev&m=110726809431611&w=2

bingo, that fixes it. too bad neither this patch nor the removal of the 
NAPI config option made it into 2.6.11...

>>   also, does this affect the e1000 driver in any way?

> No.  e1000 is a totally different driver/device with very similar name.

too bad, i was hoping for an explanation for some unexplainable crashes 
i've been experiencing... ;)

cheers
richard

Re: slab corruption in skb allocs

[Scott Feldman]

On Mar 6, 2005, at 10:40 AM, Richard Fuchs wrote:

> Scott Feldman wrote:
>> A bug in the driver.  I have a hunch: please try this patch with 
>> 2.6.9 or higher:
>> http://marc.theaimsgroup.com/?l=linux-netdev&m=110726809431611&w=2
>
> bingo, that fixes it. too bad neither this patch nor the removal of 
> the NAPI config option made it into 2.6.11...

Jesse Brandeburg @ Intel found the fix for the bug but I don't think 
it's been pushed out to Jeff's tree yet, AFAIK.  Soon, I would guess.

Would you mind giving this patch a try against 2.6.11?  I think it's 
equivalent to Jesse's patch, but less intrusive to the driver.

--- linux-2.6.11/drivers/net/e100.c.orig        Sun Mar  6 20:58:15 2005
+++ linux-2.6.11/drivers/net/e100.c     Sun Mar  6 21:01:34 2005
@@ -1471,8 +1471,12 @@ static inline int e100_rx_indicate(struc

         /* If data isn't ready, nothing to indicate */
         if(unlikely(!(rfd_status & cb_complete)))
-               return -EAGAIN;
+               return -ENODATA;

+       /* This allows for a fast restart without re-enabling 
interrupts */
+       if(le16_to_cpu(rfd->command) & cb_el)
+               nic->ru_running = 0;
+
         /* Get actual data size */
         actual_size = le16_to_cpu(rfd->actual_size) & 0x3FFF;
         if(unlikely(actual_size > RFD_BUF_LEN - sizeof(struct rfd)))
@@ -1527,7 +1531,11 @@ static inline void e100_rx_clean(struct
                         break; /* Better luck next time (see watchdog) 
*/
         }

-       e100_start_receiver(nic);
+       /* NAPI: attempt to restart the receiver iff the list is
+        * totally clean otherwise we'll race between hardware and
+        * nic->rx_to_clean. */
+       if(!work_done || *work_done == 0)
+               e100_start_receiver(nic);
  }

  static void e100_rx_clean_list(struct nic *nic)


>> No.  e1000 is a totally different driver/device with very similar 
>> name.
>
> too bad, i was hoping for an explanation for some unexplainable 
> crashes i've been experiencing... ;)

Take the e1000 issue to linux-netdev.

-scott

Re: slab corruption in skb allocs

[Richard Fuchs]

Scott Feldman wrote:

> Would you mind giving this patch a try against 2.6.11?  I think it's 
> equivalent to Jesse's patch, but less intrusive to the driver.

looks good, no more memory corruption errors. thanks for this.

cheers
richard

Re: slab corruption in skb allocs

[Andrew Morton]

Richard Fuchs <richard.fuchs@inode.info> wrote:
>
> he memory allocation debugger gives me the following messages under a
> vanilla 2.6.10 and 2.6.11 kernel when doing
> 
> 1) hdparm -d0 on my hard disk
> 2) tar c / > /dev/null
> 3) sending lots of network traffic to the machine (e.g. close to 100
> mbit/s udp packets)
> 

We ended up deciding that this was a bug in the e100 NAPI implementation.

I have a not-very-official patch in -mm, at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm1/broken-out/e100-napi-state-machine-fix.patch.
Would you be able to test that?

AFAIK there has been no official fix for this yet.