From: Joel Becker <boel.becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
tao.ma@oracle.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [GIT PULL] ocfs2 symlink walk fix
Date: Wed, 29 Sep 2010 19:07:51 -0700 [thread overview]
Message-ID: <20100930020749.GD23107@mail.oracle.com> (raw)
Linus, et al,
We've discovered that ocfs2 can walk off the end reading a fast
symlink if the NUL got corrupted on disk. It's a simple
strlen()->strnlen() fix, but I think it should go sooner rather than
later.
Please pull.
Joel
The following changes since commit 4193d9163582b05e33aca3392e46649e5c3da8d1:
Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs (2010-09-29 14:58:11 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git fixes
Joel Becker (1):
ocfs2: Don't walk off the end of fast symlinks.
fs/ocfs2/symlink.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
reply other threads:[~2010-09-30 2:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100930020749.GD23107@mail.oracle.com \
--to=boel.becker@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=tao.ma@oracle.com \
--cc=torvalds@linux-foundation.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).