tr2: log parent process name
It can be useful to tell who invoked Git - was it invoked manually by a
user via CLI or script? By an IDE? In some cases - like 'repo' tool -
we can influence the source code and set the GIT_TRACE2_PARENT_SID
environment variable from the caller process. In 'repo''s case, that
parent SID is manipulated to include the string "repo", which means we
can positively identify when Git was invoked by 'repo' tool. However,
identifying parents that way requires both that we know which tools
invoke Git and that we have the ability to modify the source code of
those tools. It cannot scale to keep up with the various IDEs and
wrappers which use Git, most of which we don't know about. Learning
which tools and wrappers invoke Git, and how, would give us insight to
decide where to improve Git's usability and performance.
Unfortunately, there's no cross-platform reliable way to gather the name
of the parent process. If procfs is present, we can use that; otherwise
we will need to discover the name another way. However, the process ID
should be sufficient to look up the process name on most platforms, so
that code may be shareable.
Git for Windows gathers similar information and logs it as a "data_json"
event. However, since "data_json" has a variable format, it is difficult
to parse effectively in some languages; instead, let's pursue a
dedicated "cmd_ancestry" event to record information about the ancestry
of the current process and a consistent, parseable way.
Git for Windows also gathers information about more than one generation
of parent. In Linux further ancestry info can be gathered with procfs,
but it's unwieldy to do so. In the interest of later moving Git for
Windows ancestry logging to the 'cmd_ancestry' event, and in the
interest of later adding more ancestry to the Linux implementation - or
of adding this functionality to other platforms which have an easier
time walking the process tree - let's make 'cmd_ancestry' accept an
array of parentage.
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-07-22 04:27:07 +03:00
|
|
|
#include "cache.h"
|
|
|
|
|
|
|
|
|
|
#include "strbuf.h"
|
|
|
|
|
#include "strvec.h"
|
|
|
|
|
#include "trace2.h"
|
|
|
|
|
|
|
|
|
|
static void get_ancestry_names(struct strvec *names)
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* NEEDSWORK: We could gather the entire pstree into an array to match
|
|
|
|
|
* functionality with compat/win32/trace2_win32_process_info.c.
|
|
|
|
|
* To do so, we may want to examine /proc/<pid>/stat. For now, just
|
|
|
|
|
* gather the immediate parent name which is readily accessible from
|
|
|
|
|
* /proc/$(getppid())/comm.
|
|
|
|
|
*/
|
|
|
|
|
struct strbuf procfs_path = STRBUF_INIT;
|
|
|
|
|
struct strbuf name = STRBUF_INIT;
|
|
|
|
|
|
|
|
|
|
/* try to use procfs if it's present. */
|
|
|
|
|
strbuf_addf(&procfs_path, "/proc/%d/comm", getppid());
|
|
|
|
|
if (strbuf_read_file(&name, procfs_path.buf, 0)) {
|
|
|
|
|
strbuf_release(&procfs_path);
|
|
|
|
|
strbuf_trim_trailing_newline(&name);
|
|
|
|
|
strvec_push(names, strbuf_detach(&name, NULL));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void trace2_collect_process_info(enum trace2_process_info_reason reason)
|
|
|
|
|
{
|
|
|
|
|
if (!trace2_is_enabled())
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
if (reason == TRACE2_PROCESS_INFO_EXIT)
|
2021-08-27 11:02:14 +03:00
|
|
|
/*
|
|
|
|
|
* The Windows version of this calls its
|
|
|
|
|
* get_peak_memory_info() here. We may want to insert
|
|
|
|
|
* similar process-end statistics here in the future.
|
|
|
|
|
*/
|
tr2: log parent process name
It can be useful to tell who invoked Git - was it invoked manually by a
user via CLI or script? By an IDE? In some cases - like 'repo' tool -
we can influence the source code and set the GIT_TRACE2_PARENT_SID
environment variable from the caller process. In 'repo''s case, that
parent SID is manipulated to include the string "repo", which means we
can positively identify when Git was invoked by 'repo' tool. However,
identifying parents that way requires both that we know which tools
invoke Git and that we have the ability to modify the source code of
those tools. It cannot scale to keep up with the various IDEs and
wrappers which use Git, most of which we don't know about. Learning
which tools and wrappers invoke Git, and how, would give us insight to
decide where to improve Git's usability and performance.
Unfortunately, there's no cross-platform reliable way to gather the name
of the parent process. If procfs is present, we can use that; otherwise
we will need to discover the name another way. However, the process ID
should be sufficient to look up the process name on most platforms, so
that code may be shareable.
Git for Windows gathers similar information and logs it as a "data_json"
event. However, since "data_json" has a variable format, it is difficult
to parse effectively in some languages; instead, let's pursue a
dedicated "cmd_ancestry" event to record information about the ancestry
of the current process and a consistent, parseable way.
Git for Windows also gathers information about more than one generation
of parent. In Linux further ancestry info can be gathered with procfs,
but it's unwieldy to do so. In the interest of later moving Git for
Windows ancestry logging to the 'cmd_ancestry' event, and in the
interest of later adding more ancestry to the Linux implementation - or
of adding this functionality to other platforms which have an easier
time walking the process tree - let's make 'cmd_ancestry' accept an
array of parentage.
Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-07-22 04:27:07 +03:00
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
if (reason == TRACE2_PROCESS_INFO_STARTUP) {
|
|
|
|
|
/*
|
|
|
|
|
* NEEDSWORK: we could do the entire ptree in an array instead,
|
|
|
|
|
* see compat/win32/trace2_win32_process_info.c.
|
|
|
|
|
*/
|
|
|
|
|
struct strvec names = STRVEC_INIT;
|
|
|
|
|
|
|
|
|
|
get_ancestry_names(&names);
|
|
|
|
|
|
|
|
|
|
if (names.nr)
|
|
|
|
|
trace2_cmd_ancestry(names.v);
|
|
|
|
|
strvec_clear(&names);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return;
|
|
|
|
|
}
|
