From: Jeff Layton <jlayton@kernel.org>
To: linux-kernel@vger.kernel.org, ceph-devel@vger.kernel.org
Cc: idryomov@gmail.com, zyan@redhat.com, sage@redhat.com,
agruenba@redhat.com, joe@perches.com, geert+renesas@glider.be,
andriy.shevchenko@linux.intel.com
Subject: [PATCH v3 0/2] ceph: don't NULL terminate virtual xattr values
Date: Fri, 21 Jun 2019 10:18:31 -0400 [thread overview]
Message-ID: <20190621141833.17551-1-jlayton@kernel.org> (raw)
v3: switch to using an intermediate buffer for snprintf destination
add patch to fix ceph_vxattrcb_layout return value
v2: drop bogus EXPORT_SYMBOL of static function
This is the 3rd posting of this patchset. Instead of adding a new
snprintf variant that doesn't NULL terminate, this set instead has
the vxattr handlers use an intermediate buffer as the snprintf
destination and then memcpy's the result into the destination buffer.
Also, I added a patch to fix up the return of ceph_vxattrcb_layout. The
existing code actually worked, but relied on casting a signed negative
value to unsigned and back, which seemed a little sketchy.
Most of the rationale for this set is in the description of the first
patch of the series.
Jeff Layton (2):
ceph: fix buffer length handling in virtual xattrs
ceph: fix return of ceph_vxattrcb_layout
fs/ceph/xattr.c | 113 ++++++++++++++++++++++++++++++++++--------------
1 file changed, 81 insertions(+), 32 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-21 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:18 Jeff Layton [this message]
2019-06-21 14:18 ` [PATCH v3 1/2] ceph: fix buffer length handling in virtual xattrs Jeff Layton
2019-06-24 10:00 ` Ilya Dryomov
2019-06-24 10:26 ` Jeff Layton
2019-06-24 11:03 ` Ilya Dryomov
2019-06-21 14:18 ` [PATCH v3 2/2] ceph: fix return of ceph_vxattrcb_layout Jeff Layton
2019-06-24 8:56 ` [PATCH v3 0/2] ceph: don't NULL terminate virtual xattr values Yan, Zheng
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=20190621141833.17551-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=agruenba@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ceph-devel@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=idryomov@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.com \
--cc=zyan@redhat.com \
/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