From: Guillaume Nault <g.nault@alphalink.fr>
To: Murat Sezgin <msezgin@codeaurora.org>
Cc: netdev@vger.kernel.org
Subject: Re: kernel panic in pppoe_release
Date: Tue, 15 Sep 2015 20:49:59 +0200 [thread overview]
Message-ID: <20150915184959.GA2869@alphalink.fr> (raw)
In-Reply-To: <006f01d0e67c$c3d53f10$4b7fbd30$@codeaurora.org>
On Thu, Sep 03, 2015 at 12:14:32PM -0700, Murat Sezgin wrote:
> I just wonder , if the
> proposed patch by Denys Fedoryshchenko, which is below, fixes this issue
> completely.
>
> pppox_unbind_sock(sk);
> +/* Signal the death of the socket. */
> +sk->sk_state = PPPOX_DEAD;
>
> Do you have a conclusion on this bug? Is it safe to get this patch along
> with the other workqueue patches?
>
You might want to check my recent reply in the original thread:
https://marc.info/?l=linux-netdev&m=144190062507458&w=2
prev parent reply other threads:[~2015-09-15 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:14 kernel panic in pppoe_release Murat Sezgin
2015-09-15 18:49 ` Guillaume Nault [this message]
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=20150915184959.GA2869@alphalink.fr \
--to=g.nault@alphalink.fr \
--cc=msezgin@codeaurora.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).