From: Mark Salyzyn via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jan Kara <jack@suse.cz>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
Dave Kleikamp <shaggy@kernel.org>,
jfs-discussion@lists.sourceforge.net, linux-doc@vger.kernel.org,
linux-integrity@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martin Brandenburg <martin@omnibond.com>,
samba-technical@lists.samba.org,
Dominique Martinet <asmadeus@codewreck.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Howells <dhowells@redhat.com>, Chris Mason <clm@fb.com>,
"David S. Miller" <davem@davemloft.net>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Eric Paris <eparis@parisplace.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
netdev@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-afs@lists.infradead.org,
Mike Marshall <hubcap@omnibond.com>,
linux-xfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
Andreas Gruenbacher <agruenba@redhat.c>
Subject: Re: [PATCH v15 1/4] Add flags option to get xattr method paired to __vfs_getxattr
Date: Tue, 5 Nov 2019 07:37:04 -0800 [thread overview]
Message-ID: <1de43656-e751-53a2-c0da-ff44ecbabbc4@android.com> (raw)
In-Reply-To: <20191105094830.GL22379@quack2.suse.cz>
On 11/5/19 1:48 AM, Jan Kara wrote:
>> @@ -228,11 +228,11 @@ static int afs_xattr_get_yfs(const struct xattr_handler *handler,
>> break;
>> case 1:
>> data = buf;
>> - dsize = snprintf(buf, sizeof(buf), "%u", yacl->inherit_flag);
>> + dsize = scnprintf(buf, sizeof(buf), "%u", yacl->inherit_flag);
>> break;
>> case 2:
>> data = buf;
>> - dsize = snprintf(buf, sizeof(buf), "%u", yacl->num_cleaned);
>> + dsize = scnprintf(buf, sizeof(buf), "%u", yacl->num_cleaned);
>> break;
>> case 3:
> These scnprintf() changes (and there are more in the patch) probably
> shouldn't be here... Otherwise the patch still looks good to me :).
>
> Honza
>
Good catch, they were done in locality, I forgot about them, this patch
series has been living for almost a year now and time has become its
enemy ... will spin this as a separate patch. They strike as a security
issue with the possibility of fragile UAF when the code is maintained by
future selves.
-- Mark
prev parent reply other threads:[~2019-11-05 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191104215253.141818-1-salyzyn@android.com>
2019-11-04 21:52 ` [PATCH v15 1/4] Add flags option to get xattr method paired to __vfs_getxattr Mark Salyzyn via Linux-f2fs-devel
2019-11-05 9:48 ` Jan Kara
2019-11-05 15:37 ` Mark Salyzyn via Linux-f2fs-devel [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=1de43656-e751-53a2-c0da-ff44ecbabbc4@android.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=adilger.kernel@dilger.ca \
--cc=adrian.hunter@intel.com \
--cc=agruenba@redhat.c \
--cc=asmadeus@codewreck.org \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dedekind1@gmail.com \
--cc=dhowells@redhat.com \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=hubcap@omnibond.com \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-afs@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=martin@omnibond.com \
--cc=mchehab+samsung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=salyzyn@android.com \
--cc=samba-technical@lists.samba.org \
--cc=shaggy@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).