| 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 PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Dec 2014 17:47:14 -0600 From: Eric Biggers <ebiggers3@...il.com> To: Larry Finger <Larry.Finger@...inger.net> Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [BUG] rtl8192se: panic accessing unmapped memory in skb Hi, To get your patched version to work at all I had to update _rtl_pci_init_rx_ring() to account for new return value of _rtl_pci_init_one_rxdesc(). I will let you know if anything shows up in the kernel log, but I expect this is a highly sporadic problem. The system has 4 GB of memory, and I used the 3.18 kernel for 10 days prior to the panic with no issues. The panic occurred while upgrading system packages, so it's possible jhat the system was experiencing memory pressure. I upgraded from 3.17 to 3.18 on Dec 8, so I've actually only had since then to notice any bugs that may have been introduced since 3.17. It does appear there were changes made to pci.c between 3.17 and 3.18. It appears the 3.17 code will drop the incoming packet if a new skb can't be allocated, whereas the 3.18 code assumes a new skb can always be allocated. The 3.17 behavior seems more logical to me. I don't know how either of these behaviors compare to other networking drivers, however. Eric -- 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/
Powered by blists - more mailing lists