From: jcm@jonmasters.org (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: Fixing audit on ARM
Date: Sun, 29 Apr 2012 02:38:23 -0400 [thread overview]
Message-ID: <1335681504-4609-1-git-send-email-jcm@jonmasters.org> (raw)
Hi Folks,
I've been playing around with getting ARM kernels built in more standard
Fedora configurations (as have a number of other members of the Fedora
ARM community). This has turned up a bunch of problems so far, which
is both good and bad. The upside is that we can all work together to
make sure some of these non-embedded features get more testing :)
Anyway. I'm sending a trivial fix that prevents systemd going into a
forkbomb OOM tailspin on all recent Fedora ARM kernels (unless we
turn off audit). Note that the fact that this has been corrupting
userspace up to this point suggests strongly to me that we should
be also considering turning off audit on ARM systems until it is
known that there are not other issues. But I can run my test
system successfully, so I submit this fix for review anyway.
Thanks,
Jon.
next reply other threads:[~2012-04-29 6:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 6:38 Jon Masters [this message]
2012-04-29 6:38 ` [PATCH] ARM: Fix restoration of IP scratch register when auditing syscalls Jon Masters
2012-04-30 10:07 ` Will Deacon
2012-04-30 18:55 ` Jon Masters
2012-05-01 11:07 ` Will Deacon
2012-05-01 11:37 ` Russell King - ARM Linux
2012-05-01 16:52 ` Jon Masters
2012-05-02 6:27 ` Jon Masters
2012-05-02 8:58 ` Will Deacon
2012-05-02 14:10 ` Jon Masters
2012-05-02 14:48 ` Eric Paris
2012-05-02 15:39 ` Will Deacon
2012-05-02 17:37 ` Jon Masters
2012-04-30 19:00 ` Russell King - ARM Linux
2012-05-03 2:59 ` Jon Masters
2012-05-03 3:03 ` Al Viro
2012-05-03 8:55 ` Will Deacon
2012-05-03 7:34 ` Russell King - ARM Linux
2012-05-02 6:22 ` Jon Masters
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=1335681504-4609-1-git-send-email-jcm@jonmasters.org \
--to=jcm@jonmasters.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).