From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] tst_ncpus_max: use kernel_max if available
Date: Tue, 26 Aug 2014 12:55:16 +0200 [thread overview]
Message-ID: <20140826105516.GA28025@rei> (raw)
In-Reply-To: <1144259951.13045166.1409048187591.JavaMail.zimbra@redhat.com>
Hi!
> These two are still open / under discussion:
> [PATCH] sbrk02: check for ret code in setup()
> [PATCH] mmap15: don't fail if mmap returns EINVAL
>
> mmap15 looks like old issue, so it could wait after release.
Agreed.
> sbrk02 can loop indefinitely in setup(), which is worse IMO.
Ok.
So the issue there is that sbrk() does not fail in setup() because
the increment overflows.
Does it work if we stop increasing the increment before that happen? Or
does sbrk() fails to fail there?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-08-26 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 10:01 [LTP] [PATCH] tst_ncpus_max: use kernel_max if available Jan Stancek
2014-08-26 10:06 ` chrubis
[not found] ` <1144259951.13045166.1409048187591.JavaMail.zimbra@redhat.com>
2014-08-26 10:55 ` chrubis [this message]
[not found] ` <1485901937.13089374.1409051869026.JavaMail.zimbra@redhat.com>
2014-08-26 11:24 ` chrubis
[not found] ` <555448176.13093369.1409052507826.JavaMail.zimbra@redhat.com>
2014-08-26 13:51 ` chrubis
2014-08-26 15:42 ` chrubis
2014-08-27 7:41 ` chrubis
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=20140826105516.GA28025@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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