From: Eric Biggers <ebiggers3@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] rtl8192se: panic accessing unmapped memory in skb
Date: Sun, 21 Dec 2014 17:47:14 -0600 [thread overview]
Message-ID: <20141221234714.GA30675@zzz> (raw)
In-Reply-To: <5497516A.2020400@lwfinger.net>
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
next prev parent reply other threads:[~2014-12-21 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 17:25 [BUG] rtl8192se: panic accessing unmapped memory in skb Eric Biggers
2014-12-21 23:02 ` Larry Finger
2014-12-21 23:47 ` Eric Biggers [this message]
2014-12-22 17:43 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141221234714.GA30675@zzz \
--to=ebiggers3@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).