public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: secret <andreas-stoewing@web.de>
To: stable@vger.kernel.org
Subject: Kernel 5.4.134
Date: Thu, 22 Jul 2021 12:09:54 +0000	[thread overview]
Message-ID: <202107221209.57475.andreas-stoewing@web.de> (raw)



Hello,

I write again the content of my last E-mail to you, for  my smartphone has got
only a small display and therefore a quit tiny keyboard...

Whenever Tor from rosa2016.1 (Rosalabs.ru) and/or Enterprise Linux 6 is
starting, at least three kernel-processes start too and/or become more than
active (CPU capacity lies by more than 10 percent, making my orange LED on the
tower blinking a lot)!

So they have got root-rights!

Their name is like kworker-kcryptd/..., dmcrypt/... and uksmd, but this is not
their complete name.

I do not want this activity as they irritate a lot in possibly causing high
and highest risks!

Tests have shown, that no data seems to get transferred over the net, but
knows the hell, what's really going on here....

Is it worth a patch for you,
can you resp. your foundation patch it?

I would appreciate this.

Regards, Andreas

I also like to tell you, that this Tor is surrounded by firejail from pclos,
this is PCLinuxOS 2021. The processes get permanently highly active for about
five (5) minutes. The LED on the tower for read and write on storage media is
really blinking madly hard all this time, while the process-manager confirms
the whole mysterious process-activities!
After this time, Tor and surfing in the internet with the browser do work fine
as much as the rest of the Linux. So I have to wait several minutes.
Does it have to do with one of the last patches of 5.4, for example the one
for dmcrypt? Anyhow I use full system encryption by LUKS, that might matte
here.

Regards,
Andreas Stöwing
(Gooken)
https://gooken.safe-ws.de/gooken

                 reply	other threads:[~2021-07-22 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202107221209.57475.andreas-stoewing@web.de \
    --to=andreas-stoewing@web.de \
    --cc=stable@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