From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] Fix tst-aio7.
Date: Thu, 06 Mar 2003 20:21:00 -0000 [thread overview]
Message-ID: <200303062021.h26KL7521950@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Thursday, 6 March 2003 11:57:23 -0800 <3E67A823.9030102@redhat.com>
> Then these variables have to have global scope.
>
> The test in question was also testing that the AIO handling at exit time
> is leak-free. There is not explicit test but one easily sees system
> resources being depleated. This is important once we have a
> kernel-supported AIO implementation.
Ok. I've reverted the aio_cancel change and instead given CB1 permanent
extent so that it's valid. I put in a comment mentioning this rationale.
prev parent reply other threads:[~2003-03-06 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 15:11 Martin Schwidefsky
2003-03-06 19:17 ` Roland McGrath
2003-03-06 19:32 ` Ulrich Drepper
2003-03-06 19:37 ` Roland McGrath
2003-03-06 19:56 ` Ulrich Drepper
2003-03-06 20:21 ` Roland McGrath [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=200303062021.h26KL7521950@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).