linux-kernel - Re: Weird kernel 2.6.17.[67] behaviour

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Jul 2006 01:15:32 +0200
From:	Sébastien Bernard <seb@...nkengul.org>
To:	debian-sparc@...ts.debian.org, linux-kernel@...r.kernel.org
Subject: Re: Weird kernel 2.6.17.[67] behaviour

seb@...nkengul.org a écrit :
> I got a perfectly workable kernel 2.6.17.1 using mkinitramfs on my U60.
> 
> I applied 2 days ago the patches to update the kernel to the 2.6.17.7.
> And to my surprise when rebooting, the boot process hanged for now
> reason.
> 
> More surprising is that when boot continues if I press one key on the
> keyboard or one button on the mouse.
> 
> The hangs happens several times in the start process and each time the
> boot resume when I press a key or a button.
> 
> I never saw such a behaviour and was looking forward the change that
> caused this.
> 
> It is not the compiler since it is the same version used for building
> the 2.6.17.1 and this one is working.
> 
> It is not the mkinitramfs tools since I tried the yaird to regenerate a
> new initrd and it hangs in the same way.
> 
> Can you shed some lights on this dark corner of linux ?
> 
> 	Seb
> 
> 

I have searched which patch is the culprit.
I appears that the 2.6.17.3 kernel is OK and the 2.6.17.4 is showing the
problem..


diff --git a/kernel/sys.c b/kernel/sys.c
index 0b6ec0e..59273f7 100644
--- a/kernel/sys.c
+++ b/kernel/sys.c
@@ -1991,7 +1991,7 @@ asmlinkage long sys_prctl(int option, un
                        error = current->mm->dumpable;
                        break;
                case PR_SET_DUMPABLE:
-                       if (arg2 < 0 || arg2 > 2) {
+                       if (arg2 < 0 || arg2 > 1) {
                                error = -EINVAL;
                                break;
                        }

I've checked and this is really the culprit.
Recompiling the 2.6.17.7 whith the patch reversed got the kernel on
track again.

I can't figure why this cause the problem.
Can you have an explanation for this ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/