From: Mark Salyzyn <salyzyn@android.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-team@android.com, linux-fsdevel@vger.kernel.org,
David Howells <dhowells@redhat.com>,
linux-afs@lists.infradead.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] afs: xattr: use scnprintf
Date: Tue, 5 Nov 2019 07:56:28 -0800 [thread overview]
Message-ID: <2e530f62-89bc-4314-8e78-e5cc049c5d69@android.com> (raw)
In-Reply-To: <20191105154850.187723-1-salyzyn@android.com>
On 11/5/19 7:48 AM, Mark Salyzyn wrote:
> sprintf and snprintf are fragile in future maintenance, switch to
> using scnprintf to ensure no accidental Use After Free conditions
> are introduced.
Urrrk Out of band stack access ...
-- Mark
prev parent reply other threads:[~2019-11-05 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:48 [PATCH] afs: xattr: use scnprintf Mark Salyzyn
2019-11-05 15:56 ` Mark Salyzyn [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=2e530f62-89bc-4314-8e78-e5cc049c5d69@android.com \
--to=salyzyn@android.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=kernel-team@android.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).