Message-Id: <202107241127.37992.andreas-stoewing@web.de>
Date:   Sat, 24 Jul 2021 11:27:34 +0000
From:   secret <andreas-stoewing@....de>
To:     linux-kernel@...r.kernel.org
Subject: ???UNSURE??? Re: Kernel 5.10.52

Date: 24.07.2021

Hi, Greg, dear Linux experts and friends,

refering to kernel 5.4, the problem with the highly active root-processes
(making the tower-LED for readwrites blink so serious hard)
listed below, tor needs the mentioned time (of about 5 to 10 minutes) to build
up a first secure connections too!

libapparmor.so.1 required by firejail (OpenSuSE 15.X) needed by tor
(rosa2016.1, mga7) must be the cause for the behaviour of the processes! I
have got no other explanation.

Kernel security module apparmor itself got deactivated within the kernel by my
boot-parameters "secure=none" and "apparmor=none".

After tor and firejail version got changed from OpenSuSE 15.X to mga7, such
root-processes did not get activated!

Now everything works fine!

But I still awaint your patches for kernel-5.4.134...

Regards
Andreas Stöwing, Mönchengladbach







------------------------


Back to my e-mail refering to kernel 5.4.134 (pclos)

The unwanted, highly activated root-processes by tor (pclos, mga7) are


kworker/u2:1-kcryptd/253:2 (escpecially this one, CPU: > 10%)
kworker/0:1H-kblockd
dmcrypt_write/2
jbd2/dm2--8

This occurs since kernel around 5.4.130.

Please patch the kernel-5.4 to prevent it in future!
Regards,

Andreas Stöwing



Hi,

This is the friendly email-bot of Greg Kroah-Hartman's inbox.  I've
detected that you have sent him a direct question that might be better
sent to a public mailing list which is much faster in responding to
questions than Greg normally is.

Please try asking one of the following mailing lists for your questions:

  For udev and hotplug related questions, please ask on the
  linux-hotplug@...r.kernel.org mailing list

  For USB related questions, please ask on the linux-usb@...r.kernel.org
  mailing list

  For PCI related questions, please ask on the
  linux-pci@...r.kernel.org or linux-kernel@...r.kernel.org mailing
  lists

  For serial and tty related questions, please ask on the
  linux-serial@...r.kernel.org mailing list.

  For staging tree related questions, please ask on the
  devel@...uxdriverproject.org mailing list.

  For general kernel related questions, please ask on the
  kernelnewbies@...linux.org or linux-kernel@...r.kernel.org mailing
  lists, depending on the type of question.  More basic, beginner
  questions are better asked on the kernelnewbies list, after reading
  the wiki at www.kernelnewbies.org.

  For Linux stable and longterm kernel release questions or patches to
  be included in the stable or longterm kernel trees, please email
  stable@...r.kernel.org and Cc: the linux-kernel@...r.kernel.org
  mailing list so all of the stable kernel developers can be notified.
  Also please read Documentation/process/stable-kernel-rules.rst in the
  Linux kernel tree for the proper procedure to get patches accepted
  into the stable or longterm kernel releases.

If you really want to ask Greg the question, please read the following
two links as to why emailing a single person directly is usually not a
good thing, and causes extra work on a single person:
	http://www.arm.linux.org.uk/news/?newsitem=11
	http://www.eyrie.org/~eagle/faqs/questions.html

After reading those messages, and you still feel that you want to email
Greg instead of posting on a mailing list, then resend your message
within 24 hours and it will go through to him.  But be forewarned, his
email inbox currently looks like:
	912 messages in /home/greg/mail/INBOX/
so it might be a while before he gets to the message.

Thank you for your understanding.

The email triggering this response has been automatically discarded.

thanks,

greg k-h's email bot

Powered by blists - more mailing lists