From: Mark Salyzyn <salyzyn@android.com>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: refcount_t + (resend to wider audience)
Date: Fri, 28 Jul 2017 12:59:47 -0700 [thread overview]
Message-ID: <0eba17bc-218e-c45c-5a49-9313126cd018@android.com> (raw)
In-Reply-To: <20170728.123139.1354715651678675641.davem@davemloft.net>
On 07/28/2017 12:31 PM, David Miller wrote:
> Sorry, even with this explanation this -stable require is completely
> and totally inappropriate.
Puts me between a rock and a hard place trying to address kernel
security issues. Should I instead file KASAN Use-After-Free reports on
stable kernels here for analysis by those with more wisdom to help
refine a more targeted fix?
For instance a dive on one of them did turn up
89e357d83c06b6fac581c3ca7f0ee3ae7e67109e which stopped an unbounded
refcounter by preventing multiple dump requests at the same time. But
the other 4 KASAN reports I focused on this week, we were not so lucky.
> You guys are really pushing things way too far with this refcount_t
> stuff, seriously.
First round ever on this, I guess I am missing some turmoil, history or
bad blood over refcount_t. Always fun to step on a landmine :-)
> NACK.
Please, guidance on where I can go from here.
Sincerely -- Mark Salyzyn
next prev parent reply other threads:[~2017-07-28 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cc109bec-d4bb-8965-3169-fe36d85e6e19@android.com>
2017-07-28 17:15 ` refcount_t + (resend to wider audience) Mark Salyzyn
2017-07-28 17:41 ` Andrew Lunn
2017-07-28 18:07 ` Mark Salyzyn
2017-07-28 19:31 ` David Miller
2017-07-28 19:59 ` Mark Salyzyn [this message]
2017-07-28 21:23 ` Andrew Lunn
2017-07-28 19:29 ` David Miller
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=0eba17bc-218e-c45c-5a49-9313126cd018@android.com \
--to=salyzyn@android.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).