mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Harris, Robert" <robert.harris@alertlogic.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"dvhart@infradead.org" <dvhart@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Help requested: futex(..., FUTEX_WAIT_PRIVATE, ...) returns EPERM
Date: Wed, 13 Nov 2019 07:29:33 +0000	[thread overview]
Message-ID: <0FFCBE3B-65D0-493F-9DB6-D4D64218EB0D@alertlogic.com> (raw)
In-Reply-To: <E0332978-739B-4546-9C3F-975216C349D2@alertlogic.com>



> On 12 Nov 2019, at 17:40, Harris, Robert <robert.harris@alertlogic.com> wrote:
>
> I am investigating an issue on 4.9.184 in which futex() returns EPERM
> intermittently for
>
> futex(uaddr, FUTEX_WAIT_PRIVATE, val, &timeout, NULL, 0)
>
> The failure affects an application in an AWS lambda;  traditional
> debugging approaches vary from difficult to impossible.  I cannot
> reproduce the problem at will, instrument the kernel, install a new
> kernel or get an application core dump.
>
> Understanding the circumstances under which EPERM can be returned for
> FUTEX_WAIT_PRIVATE would be useful but it is not a documented failure
> mode.  I have spent some time looking through futex.c but have not
> found anything yet.  I would be grateful for a hint from someone more
> knowledgeable.
>
> Please address/cc me on any reply.

To be clear, I do mean that futex() is returning -1 and setting errno
to EPERM.

Robert
Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

  reply	other threads:[~2019-11-13  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 17:40 Harris, Robert
2019-11-13  7:29 ` Harris, Robert [this message]
2019-11-13  9:04 ` Thomas Gleixner
2019-11-13 10:15   ` Harris, Robert
2019-11-13 21:34     ` Thomas Gleixner
2019-11-13 13:29 ` Mikael Pettersson
2019-11-13 17:03   ` Harris, Robert

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=0FFCBE3B-65D0-493F-9DB6-D4D64218EB0D@alertlogic.com \
    --to=robert.harris@alertlogic.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®