From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] ipv6: Properly check reference count flag before taking reference
Date: Mon, 23 Sep 2019 17:24:31 +0200 [thread overview]
Message-ID: <CAHmME9pKWuJ+oKfrKxhrjLCEw1qcWE=sCZSLOGyUMvW+eUS2cw@mail.gmail.com> (raw)
In-Reply-To: <20190923150600.GA27191@dell5510>
Apparently even with this (certainly correct) patch attached, users
are still experiencing problems. Bug hunting continues, and I'll
report back if I figure something out.
next prev parent reply other threads:[~2019-09-23 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 14:46 [PATCH] ipv6: Properly check reference count flag before taking reference Jason A. Donenfeld
2019-09-23 15:06 ` Petr Vorel
2019-09-23 15:24 ` Jason A. Donenfeld [this message]
2019-09-25 21:37 ` Eric Dumazet
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='CAHmME9pKWuJ+oKfrKxhrjLCEw1qcWE=sCZSLOGyUMvW+eUS2cw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=stable@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).