From: "Murat Sezgin" <msezgin@codeaurora.org>
To: linux-ppp@vger.kernel.org
Subject: kernel panic in pppoe_release
Date: Fri, 28 Aug 2015 19:01:51 +0000 [thread overview]
Message-ID: <003701d0e1c3$ff960b00$fec22100$@codeaurora.org> (raw)
Hi all,
We are using 3.4.103 kernel on our openwrt router platform. In the event of
interface down, we get kernel panic in the pppoe_release() function, because
the po->pppoe_dev comes to this function as NULL and dev_put() is called
without doing any NULL check.
I see that openwrt community has done an improvement for this issue with the
following commits in 3.18 and 4.0 kernels.
https://dev.openwrt.org/changeset/45653
I back ported these commits to our kernel and they increased the issue
occurrence frequency, but they didn't fix the issue completely. I ended up
that we need a NULL check in the pppoe_release() function as well. It seems
there is still a race between the pppoe_release() and the pppoe_flush_dev().
So, added the below change, but I would like to see whether this may have
side effects or not.
Can somebody please make comments on this?
@@ -589,7 +606,7 @@ static int pppoe_release(struct socket *sock)
po = pppox_sk(sk);
- if (sk->sk_state & (PPPOX_CONNECTED | PPPOX_BOUND | PPPOX_ZOMBIE)) {
+ if (po->pppoe_dev && sk->sk_state & (PPPOX_CONNECTED | PPPOX_BOUND |
PPPOX_ZOMBIE)) {
dev_put(po->pppoe_dev);
po->pppoe_dev = NULL;
}
Regards,
Murat
next reply other threads:[~2015-08-28 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 19:01 Murat Sezgin [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-03 19:14 kernel panic in pppoe_release Murat Sezgin
2015-09-15 18:49 ` Guillaume Nault
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='003701d0e1c3$ff960b00$fec22100$@codeaurora.org' \
--to=msezgin@codeaurora.org \
--cc=linux-ppp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.