All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 2/2] msgget03: don't depend on existed shared resources
Date: Thu, 22 Jul 2021 15:01:31 +0200	[thread overview]
Message-ID: <YPlsK8fsMI8T+H7c@pevik> (raw)
In-Reply-To: <YPlhMeRRsNnemT05@yuki>

> Hi!
> > In different patch [1] (I forget you already send patches to fix this) I counted
> > items in /proc/sysvipc/shm. Not sure what is safer: <= looks a bit drastic
> > (how about bug which reports ENOSPC much earlier than it should be?), but
> > obviously new mapping from other program created in the middle of testing.

> I think that we allready discussed this in another thread:

> https://lists.linux.it/pipermail/ltp/2021-July/023831.html

Thanks, I forgot this. In that case my approach (not using <=, but count
segments in /proc/sysvipc/shm before testing) might be more precise.
But no strong feeling about that, both solutions fix the test, let's chose one
and merge.

Kind regards,
Petr

  reply	other threads:[~2021-07-22 13:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12  7:52 [LTP] [PATCH v2 1/2] shmget03: don't depend on existed shared resources Alexey Kodanev
2021-07-12  7:52 ` [LTP] [PATCH v2 2/2] msgget03: " Alexey Kodanev
2021-07-22  7:55   ` Petr Vorel
2021-07-22 12:14     ` Cyril Hrubis
2021-07-22 13:01       ` Petr Vorel [this message]
2021-07-22 13:02         ` Cyril Hrubis
2021-07-23  8:46           ` xuyang2018.jy
2021-07-23 12:24             ` Petr Vorel
2021-07-27  5:51               ` xuyang2018.jy
2021-08-04  1:45                 ` xuyang2018.jy
2021-08-04 14:48                 ` Cyril Hrubis
2021-08-04 15:45                   ` Petr Vorel
2021-08-05  3:43                   ` xuyang2018.jy
2021-08-05  6:36                     ` Petr Vorel
2021-08-05  6:58                       ` xuyang2018.jy
2021-07-23 12:11           ` Petr Vorel
2021-07-12  8:28 ` [LTP] [PATCH v2 1/2] shmget03: " Li Wang
2021-07-12  8:37   ` Alexey Kodanev
2021-07-12  8:42     ` Li Wang
2021-07-12  8:55       ` Li Wang

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=YPlsK8fsMI8T+H7c@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.