From: Shailabh Nagar <nagar@watson.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Thomas Graf <tgraf@suug.ch>,
jlan@sgi.com, pj@sgi.com, Valdis.Kletnieks@vt.edu,
balbir@in.ibm.com, csturtiv@sgi.com,
linux-kernel@vger.kernel.org, hadi@cyberus.ca,
netdev@vger.kernel.org
Subject: Re: [PATCH] per-task delay accounting taskstats interface: control exit data through cpumasks]
Date: Thu, 06 Jul 2006 18:27:49 -0400 [thread overview]
Message-ID: <44AD8E65.70006@watson.ibm.com> (raw)
In-Reply-To: <20060706144808.1dd5fadf.akpm@osdl.org>
Andrew Morton wrote:
> Thomas Graf <tgraf@suug.ch> wrote:
>
>>* Shailabh Nagar <nagar@watson.ibm.com> 2006-07-06 07:37
>>
>>>@@ -37,9 +45,26 @@ static struct nla_policy taskstats_cmd_g
>>> __read_mostly = {
>>> [TASKSTATS_CMD_ATTR_PID] = { .type = NLA_U32 },
>>> [TASKSTATS_CMD_ATTR_TGID] = { .type = NLA_U32 },
>>>+ [TASKSTATS_CMD_ATTR_REGISTER_CPUMASK] = { .type = NLA_STRING },
>>>+ [TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK] = { .type = NLA_STRING },};
>>
>>>+ na = info->attrs[TASKSTATS_CMD_ATTR_REGISTER_CPUMASK];
>>>+ if (nla_len(na) > TASKSTATS_CPUMASK_MAXLEN)
>>>+ return -E2BIG;
>>>+ rc = cpulist_parse((char *)nla_data(na), mask);
>>
>>This isn't safe, the data in the attribute is not guaranteed to be
>>NUL terminated. Still it's probably me to blame for not making
>>this more obvious in the API.
>>
>
>
> Thanks, that was an unpleasant bug.
>
>
>>I've attached a patch below extending the API to make it easier
>>for interfaces using NUL termianted strings,
>
>
> In the interests of keeping this work decoupled from netlink enhancements
> I'd propose the below.
The patch looks good. I was also thinking of simply modifying the input
to have the null termination and modify later when netlink provides
generic support.
> Is it bad to modify the data at nla_data()?
>
>
> --- a/kernel/taskstats.c~per-task-delay-accounting-taskstats-interface-control-exit-data-through-cpumasks-fix
> +++ a/kernel/taskstats.c
> @@ -299,6 +299,23 @@ cleanup:
> return 0;
> }
>
> +static int parse(struct nlattr *na, cpumask_t *mask)
> +{
> + char *data;
> + int len;
> +
> + if (na == NULL)
> + return 1;
> + len = nla_len(na);
> + if (len > TASKSTATS_CPUMASK_MAXLEN)
> + return -E2BIG;
> + if (len < 1)
> + return -EINVAL;
> + data = nla_data(na);
> + data[len - 1] = '\0';
> + return cpulist_parse(data, *mask);
> +}
> +
> static int taskstats_user_cmd(struct sk_buff *skb, struct genl_info *info)
> {
> int rc = 0;
> @@ -309,27 +326,17 @@ static int taskstats_user_cmd(struct sk_
> struct nlattr *na;
> cpumask_t mask;
>
> - if (info->attrs[TASKSTATS_CMD_ATTR_REGISTER_CPUMASK]) {
> - na = info->attrs[TASKSTATS_CMD_ATTR_REGISTER_CPUMASK];
> - if (nla_len(na) > TASKSTATS_CPUMASK_MAXLEN)
> - return -E2BIG;
> - rc = cpulist_parse((char *)nla_data(na), mask);
> - if (rc)
> - return rc;
> - rc = add_del_listener(info->snd_pid, &mask, REGISTER);
> + rc = parse(info->attrs[TASKSTATS_CMD_ATTR_REGISTER_CPUMASK], &mask);
> + if (rc < 0)
> return rc;
> - }
> + if (rc == 0)
> + return add_del_listener(info->snd_pid, &mask, REGISTER);
>
> - if (info->attrs[TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK]) {
> - na = info->attrs[TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK];
> - if (nla_len(na) > TASKSTATS_CPUMASK_MAXLEN)
> - return -E2BIG;
> - rc = cpulist_parse((char *)nla_data(na), mask);
> - if (rc)
> - return rc;
> - rc = add_del_listener(info->snd_pid, &mask, DEREGISTER);
> + rc = parse(info->attrs[TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK], &mask);
> + if (rc < 0)
> return rc;
> - }
> + if (rc == 0)
> + return add_del_listener(info->snd_pid, &mask, DEREGISTER);
>
> /*
> * Size includes space for nested attributes
> _
>
next prev parent reply other threads:[~2006-07-06 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 9:28 [PATCH] per-task delay accounting taskstats interface: control exit data through cpumasks] Shailabh Nagar
2006-07-06 9:56 ` Andrew Morton
2006-07-06 10:44 ` Shailabh Nagar
2006-07-06 11:37 ` Shailabh Nagar
2006-07-06 12:08 ` Thomas Graf
2006-07-06 13:21 ` Shailabh Nagar
2006-07-06 21:48 ` Andrew Morton
2006-07-06 22:27 ` Shailabh Nagar [this message]
2006-07-06 22:56 ` Andrew Morton
2006-07-07 10:21 ` Thomas Graf
2006-07-06 22:40 ` Thomas Graf
2006-07-06 23:05 ` Andrew Morton
2006-07-07 10:16 ` Thomas Graf
2006-07-07 6:18 ` Paul Jackson
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=44AD8E65.70006@watson.ibm.com \
--to=nagar@watson.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=csturtiv@sgi.com \
--cc=hadi@cyberus.ca \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pj@sgi.com \
--cc=tgraf@suug.ch \
/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).