From: "Theodore Ts'o" <tytso@mit.edu>
To: secret <andreas-stoewing@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ???UNSURE??? Re: Unwanted activation of root-processes getting highly activated
Date: Thu, 14 Oct 2021 14:27:08 -0400 [thread overview]
Message-ID: <YWh2fO8/M82GxXZe@mit.edu> (raw)
In-Reply-To: <202110141240.12172.andreas-stoewing@web.de>
On Thu, Oct 14, 2021 at 12:40:08PM +0000, secret wrote:
> Hi,
> Firejail must have caused the high activity.
> Whenever I stop it (process firejail), they lower to origin.
This is what I had been trying to tell you repeatedly. Firejail
(firefox run in a sandbox/jail) is a browser which will do various
activities on behalf of whatever web pages that you visit. Some of
these webpages may have javascript, or other web-based application
code which is causing a lot of file I/O. So when visiting that web
page causes firefox to execute a lot of file I/O, on behalf of the web
site, in order to service the file I/O, the kernel will do that work
in the kernel threads that you seem to be objecting to having
activity.
However, those kernel threads being active when there is file I/O is
*normal*. It is the system working as intended. I don't know why you
would be objecting to those kernel threads being active, but if you
don't like it, don't do any file I/O, and if that means not using
firefox (or "firejail") to visit those web sites.
Regards,
- Ted
next prev parent reply other threads:[~2021-10-14 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 12:40 ???UNSURE??? Re: Unwanted activation of root-processes getting highly activated secret
2021-10-14 18:27 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-14 13:43 secret
2021-10-15 16:35 andreas-stoewing
2021-10-28 9:44 secret
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=YWh2fO8/M82GxXZe@mit.edu \
--to=tytso@mit.edu \
--cc=andreas-stoewing@web.de \
--cc=linux-kernel@vger.kernel.org \
/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