From: Paul Moore <paul@paul-moore.com>
To: "Ján Stanček" <jan.stancek@gmail.com>
Cc: netdev@vger.kernel.org, eparis@redhat.com, sds@tycho.nsa.gov
Subject: Re: NULL pointer deref, selinux_socket_unix_may_send+0x34/0x90
Date: Fri, 22 Mar 2013 12:24:38 -0400 [thread overview]
Message-ID: <3405435.XFBqjMtCVW@sifl> (raw)
In-Reply-To: <CAMpz-8bzjyBzk+mkaR-hHndtRZVyTb0LX8idEvypRV-itdSRYw@mail.gmail.com>
On Friday, March 22, 2013 04:48:32 PM Ján Stanček wrote:
> Hi Paul,
>
> thanks for reply, I'll try your patch and let you know.
Great, thanks.
> I'm not certain about cause either, but patch I sent in last email
> makes it go away, so maybe that can help in some way.
At the very least you've found a way to reproduce the problem and your patch
furthers my belief that we've got a race condition somewhere - all very
helpful! It may also turn out that your patch is the "right" solution, I'd
just like to better understand why we are seeing the race in the first place.
> I made a v2 of the reproducer (attached), which triggers the issue a lot
> faster on 2 systems I tried (32 CPU and 4 CPU systems) - just in couple of
> seconds.
Excellent, while I don't have a 32 cpu system handy, I do have a 4 cpu system
that I can play with. Thanks again.
-Paul
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2013-03-22 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 22:19 NULL pointer deref, selinux_socket_unix_may_send+0x34/0x90 Ján Stanček
2013-03-22 15:24 ` Paul Moore
2013-03-22 15:48 ` Ján Stanček
2013-03-22 16:24 ` Paul Moore [this message]
2013-03-22 16:52 ` Ján Stanček
2013-03-22 18:24 ` Paul Moore
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=3405435.XFBqjMtCVW@sifl \
--to=paul@paul-moore.com \
--cc=eparis@redhat.com \
--cc=jan.stancek@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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