From: "Duane Griffin" <duaneg@dghda.com>
To: "Andreas Dilger" <adilger@sun.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] vfs: introduce helper function to safely NUL-terminate symlinks
Date: Wed, 17 Dec 2008 00:26:57 +0000 [thread overview]
Message-ID: <e9e943910812161626i6f2cdc3eldc36c68e9a98f180@mail.gmail.com> (raw)
In-Reply-To: <20081216234638.GX5000@webber.adilger.int>
2008/12/16 Andreas Dilger <adilger@sun.com>:
> On Dec 16, 2008 15:51 +0000, Duane Griffin wrote:
>> A number of filesystems were potentially triggering kernel bugs due to
>> corrupted symlink names on disk. This helper helps safely terminate the
>> names.
>>
>> +static inline void nd_terminate_link(void *name,unsigned len,unsigned maxlen)
>> +{
>> + ((char *) name)[min(len, maxlen)] = '\0';
>> +}
>
>> @@ -4200,9 +4201,11 @@ struct inode *ext4_iget(struct super_block *sb, unsigned long ino)
>> } else if (S_ISLNK(inode->i_mode)) {
>> + if (ext4_inode_is_fast_symlink(inode)) {
>> inode->i_op = &ext4_fast_symlink_inode_operations;
>> + nd_terminate_link(ei->i_data, inode->i_size,
>> + sizeof(ei->i_data));
>> + } else {
>> inode->i_op = &ext4_symlink_inode_operations;
>> ext4_set_aops(inode);
>> }
>
> With sizeof(ei->i_data) = 15 * 4 = 60 bytes, this will set ei->i_data[60]
> as NUL, which is writing 1 byte beyond the end of the array.
Argh, you are correct, of course.
> Note that in ext[234]_symlink() the check for fast symlinks is:
>
> l = strlen(symname)+1;
> if (l > sizeof (EXT3_I(inode)->i_data)) {
> inode->i_op = &ext3_symlink_inode_operations;
> } else {
> inode->i_op = &ext3_fast_symlink_inode_operations;
> inode->i_size = l-1;
> }
>
> so in fact the fast symlinks should always have space for a trailing NUL
> character, and "sizeof(ei->i_data) - 1" is the right maxlen to use for
> ext[234].
>
> That might not be true for other filesystems, in which case you would
> need to add a "padding" field after the symlink name in memory to hold
> the trailing NUL.
It is true for sysv, too. The ufs code also, but that has other
issues, anyway. The generic page symlink and freevxfs patches should
be fine, though.
Cheers,
Duane.
--
"I never could learn to drink that blood and call it wine" - Bob Dylan
next prev parent reply other threads:[~2008-12-17 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1229442720-31056-1-git-send-email-duaneg@dghda.com>
[not found] ` <1229442720-31056-2-git-send-email-duaneg@dghda.com>
[not found] ` <1229442720-31056-3-git-send-email-duaneg@dghda.com>
[not found] ` <1229442720-31056-4-git-send-email-duaneg@dghda.com>
2008-12-16 15:51 ` [PATCH] ext3: ensure fast symlinks are NUL-terminated Duane Griffin
2008-12-16 15:51 ` [PATCH] ext4: " Duane Griffin
2008-12-16 23:46 ` [PATCH] vfs: introduce helper function to safely NUL-terminate symlinks Andreas Dilger
2008-12-17 0:26 ` Duane Griffin [this message]
2008-12-19 15:03 ` Duane Griffin
2008-12-19 19:28 ` Andrew Morton
2008-12-19 19:43 ` Al Viro
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=e9e943910812161626i6f2cdc3eldc36c68e9a98f180@mail.gmail.com \
--to=duaneg@dghda.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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