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-prev] [day] [month] [year] [list]
Message-ID: <80040.1221501535@turing-police.cc.vt.edu>
Date:	Mon, 15 Sep 2008 13:58:55 -0400
From:	Valdis.Kletnieks@...edu
To:	Frank Mayhar <fmayhar@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.27-rc6-mmotm0913 build error - suspect itimers-fix-itimer-many-thread-hang.patch

On Mon, 15 Sep 2008 10:13:24 PDT, Frank Mayhar said:

> As it happens, my top-of-tree snapshot is missing this routine.  I'm
> re-snapping it now but I think you're right that it's a merge issue with
> linux-next.  The fix, however, is trivial:  Replace the entire if block
> with the line:
> 	update_rlimit_cpu(rlim->rlim_cur);
> 
> The above snippet becomes:
> 
>        if (rc) {
>                 for (i = 0; i < RLIM_NLIMITS; i++) {
>                         rlim = current->signal->rlim + i;
>                         initrlim = init_task.signal->rlim+i;
>                         rlim->rlim_cur = min(rlim->rlim_max, initrlim->rlim_cur);
>                 }
>                 update_rlimit_cpu(rlim->rlim_cur);
>         }
> 
> And double-check that linux/posix-timers.h is being #included around
> line 80.

Yeah, it had the #include already, and with the above fix, I actually got a
clean build of the kernel.  Boot testing will have to wait till tonight...

Thanks for the help. :)

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ