From: Roland McGrath <roland@redhat.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix sigqueue accounting for posix-timers broken by new RLIMIT_SIGPENDING tracking code
Date: Fri, 10 Sep 2004 12:24:59 -0700 [thread overview]
Message-ID: <200409101924.i8AJOxRH029788@magilla.sf.frob.com> (raw)
In-Reply-To: Chris Wright's message of Friday, 10 September 2004 10:42:28 -0700 <20040910104228.K1924@build.pdx.osdl.net>
D'oh. You are right. I misread the code in the middle of the night. I
came across the new issue of hitting the sigpending limit while verifying a
test case for timers leaking. I failed to realize that it's the timer leak
itself that translates into a sigpending count leak.
Indeed, ignore that patch, and wait for the posix-timers leak fix coming soon.
Thanks,
Roland
next prev parent reply other threads:[~2004-09-10 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 5:10 Roland McGrath
2004-09-10 6:49 ` Chris Wright
2004-09-10 17:42 ` Chris Wright
2004-09-10 19:24 ` Roland McGrath [this message]
2004-09-10 19:34 ` Chris Wright
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=200409101924.i8AJOxRH029788@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®