From: Xi Wang <xi.wang@gmail.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org, Xi Wang <xi.wang@gmail.com>
Subject: [PATCH 0/3] ceph: fix multiple out-of-bounds checks
Date: Wed, 14 Dec 2011 15:24:30 -0500 [thread overview]
Message-ID: <1323894273-13904-1-git-send-email-xi.wang@gmail.com> (raw)
Fix several possible out-of-bounds pointers if the incoming message is
corrupted or malicious.
Xi Wang (3):
ceph: fix out-of-bounds pointers in parse_reply_info()
ceph: fix bounds check macros ceph_decode_need and ceph_encode_need
ceph: avoid panic with mismatched symbolic link sizes in fill_inode()
fs/ceph/inode.c | 10 +++++-----
fs/ceph/mds_client.c | 2 ++
include/linux/ceph/decode.h | 9 +++++++--
3 files changed, 14 insertions(+), 7 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-12-14 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 20:24 Xi Wang [this message]
2011-12-14 20:24 ` [PATCH 1/3] ceph: fix out-of-bounds pointers in parse_reply_info() Xi Wang
2011-12-14 20:24 ` [PATCH 2/3] ceph: fix bounds check macros ceph_decode_need and ceph_encode_need Xi Wang
2012-04-18 14:13 ` Alex Elder
2012-04-18 17:53 ` Sage Weil
2012-04-18 18:41 ` Alex Elder
2011-12-14 20:24 ` [PATCH 3/3] ceph: avoid panic with mismatched symbolic link sizes in fill_inode() Xi Wang
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=1323894273-13904-1-git-send-email-xi.wang@gmail.com \
--to=xi.wang@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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