From: "Tom Burns" <tom.i.burns@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Clarification re: outstanding IPC flaws
Date: Mon, 26 Nov 2007 12:05:31 -0500 [thread overview]
Message-ID: <671c20540711260905p11249695x9e3999bf25f3cf2@mail.gmail.com> (raw)
In-Reply-To: <671c20540711260901w6662fcabv779ce4fc51ec3d14@mail.gmail.com>
Sorry for the double post.
On Nov 26, 2007 12:01 PM, Tom Burns <tom.i.burns@gmail.com> wrote:
> I have some questions about this comment.
>
> Most importantly - does this mean that if I have multiple processes
> queued inside semop() calls with sem_val = -1 (also, if it matters,
> SEM_UNDO flag is set),
This should read "sem_op = -1" as opposed to "sem_val = -1".
Cheers,
Tom Burns
prev parent reply other threads:[~2007-11-26 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 17:01 Tom Burns
2007-11-26 17:05 ` Tom Burns [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=671c20540711260905p11249695x9e3999bf25f3cf2@mail.gmail.com \
--to=tom.i.burns@gmail.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®