From: Stephen Hemminger <stephen@networkplumber.org>
To: Kaisen You <kaisenx.you@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com, yidingx.zhou@intel.com,
stable@dpdk.org
Subject: Re: [PATCH] child process synchronization NIC startup parameters
Date: Thu, 13 Jun 2024 16:23:38 -0700 [thread overview]
Message-ID: <20240613162338.3c9f4be4@hermes.local> (raw)
In-Reply-To: <20230705093515.3285574-1-kaisenx.you@intel.com>
On Wed, 5 Jul 2023 17:35:14 +0800
Kaisen You <kaisenx.you@intel.com> wrote:
>
> +/* get cmdline form PID. Read process info form /proc/$PID. */
> +static char *get_cmdline_from_pid(pid_t pid, char *buf, int len)
> +{
> + char filename[PATH_MAX];
> + char *name = NULL;
> + int fd;
> + int ret;
> +
> + if (pid < 1 || buf == NULL || len < 0) {
> + printf("%s: illegal param\n", __func__);
> + return NULL;
> + }
> +
> + snprintf(filename, PATH_MAX, "/proc/%d/cmdline", pid);
> + memset(buf, 0, len);
> + fd = open(filename, O_RDONLY);
> + if (fd < 0) {
> + perror("open:");
> + return NULL;
> + }
> + ret = read(fd, buf, len);
> + close(fd);
> +
> + if (ret < 0)
> + return NULL;
> +
> + if (buf[ret-1] == '\n')
> + buf[--ret] = 0;
> +
> + name = buf;
> + while (ret) {
> + if (((unsigned char)*name) < ' ')
> + *name = ' ';
> + name++;
> + ret--;
> + }
> + *name = 0;
> +
> + if (buf[0])
> + return buf;
> +
> + return NULL;
> +}
Bad idea, this is not portable, and easily broken by system changes and container
environments. Please use some form of explicit communication like is done
for primary / secondary process support.
next prev parent reply other threads:[~2024-06-13 23:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 9:35 Kaisen You
2023-07-06 2:16 ` Yang, Qiming
2023-07-07 1:21 ` You, KaisenX
2023-07-06 19:07 ` Stephen Hemminger
2023-07-14 5:59 ` [PATCH v2] app/test:subprocess synchronization of parameters Kaisen You
2023-07-17 1:47 ` Kaisen You
2023-07-26 2:39 ` Kaisen You
2023-09-25 9:42 ` [PATCH v3] app/test: secondary process passes allow parameters Mingjin Ye
2023-09-25 9:58 ` David Marchand
2023-09-25 10:09 ` Ye, MingjinX
2023-09-25 10:19 ` David Marchand
2023-09-27 3:42 ` [PATCH v4] app/test: append 'allow' parameters to secondary processes Mingjin Ye
2023-10-13 2:47 ` Huang, ZhiminX
2023-11-09 11:13 ` Bruce Richardson
2023-11-10 10:30 ` [PATCH v5] app/test: secondary process passes allow parameters Mingjin Ye
2023-11-10 11:18 ` Bruce Richardson
2023-11-13 10:42 ` [PATCH v6] " Mingjin Ye
2023-11-13 11:11 ` Bruce Richardson
2023-11-14 10:28 ` [PATCH v7] " Mingjin Ye
2023-11-17 10:05 ` Huang, ZhiminX
2023-11-17 10:24 ` Ye, MingjinX
2023-11-17 11:17 ` Bruce Richardson
2023-11-24 10:28 ` Ye, MingjinX
2024-03-06 13:50 ` Thomas Monjalon
2024-10-03 16:00 ` [PATCH v2] app/test:subprocess synchronization of parameters Stephen Hemminger
2024-06-13 23:23 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-05 7:43 [PATCH] child process synchronization NIC startup parameters Kaisen You
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=20240613162338.3c9f4be4@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=kaisenx.you@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@intel.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 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).