From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: Re: [patch] ocfs2: tighten up strlen() checking
Date: Mon, 12 Jul 2010 18:33:53 +0000 [thread overview]
Message-ID: <20100712183353.GF12179@mail.oracle.com> (raw)
In-Reply-To: <20100710143336.GB19184@bicker>
On Sat, Jul 10, 2010 at 04:33:36PM +0200, Dan Carpenter wrote:
> This function is only called from one place and it's like this:
> dlm_register_domain(conn->cc_name, dlm_key, &fs_version);
>
> The "conn->cc_name" is 64 characters long. If strlen(conn->cc_name)
> were equal to O2NM_MAX_NAME_LEN (64) that would be a bug because
> strlen() doesn't count the NULL character.
>
> In fact, if you look how O2NM_MAX_NAME_LEN is used, it mostly describes
> 64 character buffers. The only exception is nd_name from struct
> o2nm_node.
>
> Anyway I looked into it and in this case the domain string comes from
> osb->uuid_str in ocfs2_setup_osb_uuid(). That's 32 characters and NULL
> which easily fits into O2NM_MAX_NAME_LEN. This patch doesn't change how
> the code works, but I think it makes the code a little cleaner.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
This patch is now in the fixes branch of ocfs2.git.
Joel
--
Viro's Razor:
Any race condition, no matter how unlikely, will occur just
often enough to bite you.
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch] ocfs2: tighten up strlen() checking
Date: Mon, 12 Jul 2010 11:33:53 -0700 [thread overview]
Message-ID: <20100712183353.GF12179@mail.oracle.com> (raw)
In-Reply-To: <20100710143336.GB19184@bicker>
On Sat, Jul 10, 2010 at 04:33:36PM +0200, Dan Carpenter wrote:
> This function is only called from one place and it's like this:
> dlm_register_domain(conn->cc_name, dlm_key, &fs_version);
>
> The "conn->cc_name" is 64 characters long. If strlen(conn->cc_name)
> were equal to O2NM_MAX_NAME_LEN (64) that would be a bug because
> strlen() doesn't count the NULL character.
>
> In fact, if you look how O2NM_MAX_NAME_LEN is used, it mostly describes
> 64 character buffers. The only exception is nd_name from struct
> o2nm_node.
>
> Anyway I looked into it and in this case the domain string comes from
> osb->uuid_str in ocfs2_setup_osb_uuid(). That's 32 characters and NULL
> which easily fits into O2NM_MAX_NAME_LEN. This patch doesn't change how
> the code works, but I think it makes the code a little cleaner.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
This patch is now in the fixes branch of ocfs2.git.
Joel
--
Viro's Razor:
Any race condition, no matter how unlikely, will occur just
often enough to bite you.
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-07-12 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 14:33 [patch] ocfs2: tighten up strlen() checking Dan Carpenter
2010-07-10 14:33 ` [Ocfs2-devel] " Dan Carpenter
2010-07-12 11:30 ` Wengang Wang
2010-07-12 11:30 ` [Ocfs2-devel] " Wengang Wang
2010-07-12 13:39 ` Dan Carpenter
2010-07-12 13:39 ` [Ocfs2-devel] " Dan Carpenter
2010-07-12 14:31 ` Wengang Wang
2010-07-12 14:31 ` [Ocfs2-devel] " Wengang Wang
2010-07-12 16:49 ` Sunil Mushran
2010-07-12 16:49 ` [Ocfs2-devel] " Sunil Mushran
2010-07-12 16:46 ` Sunil Mushran
2010-07-12 16:46 ` [Ocfs2-devel] " Sunil Mushran
2010-07-12 18:33 ` Joel Becker [this message]
2010-07-12 18:33 ` Joel Becker
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=20100712183353.GF12179@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.