Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(config): correct the truncation of process name(comm name) #737

Merged
merged 1 commit into from
Jan 18, 2025

Conversation

xcpky
Copy link

@xcpky xcpky commented Jan 17, 2025

Background

#736

Checklist

Full Changelogs

  • truncate the process name to 15 characters(previously 16)
  • issue the truncation info log whenever the process name is longer than 15 characters(previously 16)

Issue Reference

#736
#474

Closes #[736]

Test Result

add pname(systemd-resolved) -> must_direct
then all the dns traffic through systemd-resolved goes out directly
but before the PR, it doesn't.

I test the patch on main branch, because on develop branch dae errors out without this patch as

load eBPF objects: field TproxyLanEgress: program tproxy_lan_egress: load program: permission denied: misaligned stack access off

Previously dae truncate the process names in pname configs to 16 bytes
Now we truncate the name to 15 bytes because the length of the comm
name of processes in linux is 15 bytes.

This makes
`pname(systemd-resolved)`
works the same as
`pname(systemd-resolve)`

Closes daeuniverse#736, daeuniverse#474
@xcpky xcpky requested review from a team as code owners January 17, 2025 09:08
@dae-prow dae-prow bot assigned xcpky Jan 17, 2025
@xcpky xcpky changed the base branch from main to develop January 17, 2025 09:16
@xcpky xcpky requested a review from mzz2017 as a code owner January 17, 2025 09:16
Copy link
Contributor

@mzz2017 mzz2017 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mzz2017 mzz2017 merged commit eac9aac into daeuniverse:develop Jan 18, 2025
32 of 36 checks passed
@mzz2017
Copy link
Contributor

mzz2017 commented Jan 18, 2025

@xcpky 为什么合并到 develop,请发起一个到main的pr,谢谢!

@xcpky
Copy link
Author

xcpky commented Jan 18, 2025

@xcpky 为什么合并到 develop,请发起一个到main的pr,谢谢!

我是按照本项目的contribute.md的指引来的啊

Create a new branch to work on! Branch from develop if it exists, else from master.

From your fork open a pull request in the correct branch. Target the project's develop branch if there is one, else go for master!

为啥规则这里这么写呢,请您解释下,我当时还觉得奇怪。

我明天发main的pr

@mzz2017
Copy link
Contributor

mzz2017 commented Jan 19, 2025

@xcpky 可能是失误,后面会更正,请麻烦提到 main 吧

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants