From: Valdis.Kletnieks@vt.edu
To: Frank Mayhar <fmayhar@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc6-mmotm0913 build error - suspect itimers-fix-itimer-many-thread-hang.patch
Date: Mon, 15 Sep 2008 13:58:55 -0400 [thread overview]
Message-ID: <80040.1221501535@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 15 Sep 2008 10:13:24 PDT." <1221498804.19012.13.camel@bobble.smo.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
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. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2008-09-15 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 16:29 Valdis.Kletnieks
2008-09-15 17:13 ` Frank Mayhar
2008-09-15 17:58 ` Valdis.Kletnieks [this message]
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=80040.1221501535@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=fmayhar@google.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®