-by: Viktor Rosendahl [EMAIL PROTECTED]
---
security/lowmem.c | 14 ++
1 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/security/lowmem.c b/security/lowmem.c
index 2dc0c4a..183c57f 100644
--- a/security/lowmem.c
+++ b/security/lowmem.c
@@ -136,28 +136,18 @@ KERNEL_ATTR_RO
Hello,
Currently the lowmem module doesn't compile. Here are some patches
that will fix a bug, make some improvements and even make it compile.
security/lowmem.c | 258 --
1 file changed, 154 insertions(+), 104 deletions(-)
best regards,
from the oom killer should
not be denied memory either.
Signed-off-by: Henrik Saari [EMAIL PROTECTED]
Signed-off-by: Viktor Rosendahl [EMAIL PROTECTED]
---
security/lowmem.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/security/lowmem.c b/security/lowmem.c
index
+ req.func_cb = NULL;
maybe below is a better patch:
diff --git a/drivers/i2c/chips/twl4030-madc.c
b/drivers/i2c/chips/twl4030-madc.c
index 72b126b..6d8915e 100644
--- a/drivers/i2c/chips/twl4030-madc.c
+++ b/drivers/i2c/chips/twl4030-madc.c
@@ -360,7 +360,7 @@ static
req is an automatic variable and thus we cannot rely on it being initialized to
zero (I am leaving the 0!= NULL discussion aside). Other functions test
if this pointer is NULL, in order to determine whether it is a valid address or
not.
Signed-off-by: Viktor Rosendahl [EMAIL PROTECTED
Hi all,
I have seen this bug crash the kernel when the security framework is enabled
in the kernel config. It crashed with a bad syscall from the events/0
workqueue; probably because the security framework is initialized very early
and thus the stack has been used more [or differently] and we end
