Skip to content

kworker root processes stored with another name #8

@cpl-cmd

Description

@cpl-cmd

I started looking at this and I am puzzled. The kworker processes should only ever run as kernel threads as the root user and that is what I see. You are wanting to see the kworker running as the system user and that will never happen.

I will close this out.

In Linux, kworker threads are kernel worker threads, which are part of the kernel infrastructure for handling deferred work in process context (like workqueues, I/O completions, timers, etc.). They are:

Created and managed by the kernel Always run in kernel space Execute as user root (UID 0), since they're part of the kernel

I don't understand your answer.
What I meant is that the kernel root process "[kworker/u8:3-events_unbound]" which is shown clearly with the ps command with PID 2743 should be stored with that process name ("[kworker/u8:3-events_unbound]") instead of another name of another process in this case "dd if=/dev/zero of=/home/system/testfile bs=10M count=100".

I feel that there is a misunderstanding of the issue. The stored information of the process names is not coherent.

Sorry I am managing this in the wrong way, don't know how to clarify the previous issue with your response and it was closed.

Originally posted by @cpl-cmd in #7

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions