From: Rinat Gadelshin <rgadelsh@gmail.com>
To: linux-audit@redhat.com
Subject: Can AUDIT_LIST_RULES causes kthreadd-spam?
Date: Thu, 4 May 2023 00:14:08 +0300 [thread overview]
Message-ID: <ecd4bf68-3bf1-a1d8-4da5-5fbd28c51a6b@gmail.com> (raw)
Hello there =)
My name is Rinat.
I'm a newbie here (at Linux kernel developer community).
My current job is to work with audit subsystem on different
versions of Linux (and different kernel versions from 3.10 to the latest)
with and without auditd.
My program works behalf of root account and uses netlink
(unicast or multicast depends of the kernel's version)
to communicate with audit subsystem of the kernel.
If actual audit rule list has been changed
then my program should restore the configured audit rule list.
To do it the program periodically (with 60 seconds interval)
requests the actual rule list be sending AUDIT_LIST_RULES.
All rules are receiving perfectly.
But I've noticed that there are many (2K+ for 5 minutes test)
kthreadd process have been spawned after that request
(I've stubbed the poll code and compare logs).
Please, can you point me, what can I do to avoid this kthreadd-spam.
Thank you.
Best regards
Rinath
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2023-05-03 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 21:14 Rinat Gadelshin [this message]
2023-05-03 21:27 ` Can AUDIT_LIST_RULES causes kthreadd-spam? Paul Moore
2023-05-03 22:12 ` Rinat Gadelshin
2023-05-04 2:50 ` Tetsuo Handa
2023-05-04 18:40 ` Paul Moore
2023-05-04 22:53 ` Tetsuo Handa
2023-05-05 22:12 ` Rinat Gadelshin
2023-05-06 6:50 ` Tetsuo Handa
2023-05-10 12:12 ` Rinat Gadelshin
2023-05-10 13:30 ` Tetsuo Handa
2023-05-10 13:48 ` Steve Grubb
2023-05-24 10:38 ` Rinat Gadelshin
2023-05-24 10:48 ` Tetsuo Handa
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=ecd4bf68-3bf1-a1d8-4da5-5fbd28c51a6b@gmail.com \
--to=rgadelsh@gmail.com \
--cc=linux-audit@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).