From: Christoph Schulz <develop@kristov.de>
To: David Miller <davem@davemloft.net>
Cc: g.nault@alphalink.fr, netdev@vger.kernel.org, paulus@samba.org,
nuclearcat@nuclearcat.com, Matt.Bennett@alliedtelesis.co.nz
Subject: Re: [PATCH net] ppp: fix pppoe_dev deletion condition in pppoe_release()
Date: Fri, 20 Nov 2015 19:58:18 +0100 [thread overview]
Message-ID: <20151120195818.534169fzfht9eu6i@localhost> (raw)
In-Reply-To: <20151023.033048.1984003889137051787.davem@davemloft.net>
Hello!
David Miller schrieb am Fri, 23 Oct 2015 03:30:48 -0700 (PDT):
> From: Guillaume Nault <g.nault@alphalink.fr>
> Date: Thu, 22 Oct 2015 16:57:10 +0200
>
>> We can't rely on PPPOX_ZOMBIE to decide whether to clear po->pppoe_dev.
>> PPPOX_ZOMBIE can be set by pppoe_disc_rcv() even when po->pppoe_dev is
>> NULL. So we have no guarantee that (sk->sk_state & PPPOX_ZOMBIE) implies
>> (po->pppoe_dev != NULL).
>> Since we're releasing a PPPoE socket, we want to release the pppoe_dev
>> if it exists and reset sk_state to PPPOX_DEAD, no matter the previous
>> value of sk_state. So we can just check for po->pppoe_dev and avoid any
>> assumption on sk->sk_state.
>>
>> Fixes: 2b018d57ff18 ("pppoe: drop PPPOX_ZOMBIEs in pppoe_release")
>> Signed-off-by: Guillaume Nault <g.nault@alphalink.fr>
>
> Applied and queued up for -stable, thanks.
Somehow this commit (1acea4f6ce1b1c0941438aca75dd2e5c6b09db60) did not
make it into Linux 4.2.6, 4.1.13, or 3.18.24. But I don't find it in
your stable bundle on Patchwork either. Has this patch been
inadvertently "lost in translation"?
Best regards,
--
Christoph Schulz
prev parent reply other threads:[~2015-11-20 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 14:57 [PATCH net] ppp: fix pppoe_dev deletion condition in pppoe_release() Guillaume Nault
2015-10-23 10:30 ` David Miller
2015-11-20 18:58 ` Christoph Schulz [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=20151120195818.534169fzfht9eu6i@localhost \
--to=develop@kristov.de \
--cc=Matt.Bennett@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=g.nault@alphalink.fr \
--cc=netdev@vger.kernel.org \
--cc=nuclearcat@nuclearcat.com \
--cc=paulus@samba.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