From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Seebs <seebs@seebs.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pseudo: update to latest master
Date: Mon, 19 Feb 2018 11:27:56 +0200 [thread overview]
Message-ID: <bb1b003e-9bd3-f438-8ae1-637500d970b5@linux.intel.com> (raw)
In-Reply-To: <20180217141701.229759cf@seebsdell>
On 02/17/2018 10:17 PM, Seebs wrote:
>> For me, with epoll enabled:
>>
>> b6a015a works
>> 23f089f and 26e30fa both lock up
>
> Huh. It's possible that the initial "don't try to close fd 0" was
> correct, and the real problem is that the attempt is getting made
> mistakenly. I'll study that more; the epoll code was a contribution and
> I may not have fully understood it.
To be honest, it would have been better to apply my epoll patch as it
is, and then do additional modifications as separate commits. That would
make it simpler to isolate the issue. We've used my epoll patch for many
months without problems on the autobuilder and elsewhere.
Alex
next prev parent reply other threads:[~2018-02-19 9:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 9:56 [PATCH] pseudo: update to latest master Alexander Kanavin
2018-02-16 16:55 ` Martin Jansa
2018-02-16 17:26 ` Alexander Kanavin
2018-02-16 17:51 ` Seebs
2018-02-16 19:11 ` Martin Jansa
2018-02-16 19:25 ` Seebs
2018-02-17 11:22 ` Alexander Kanavin
2018-02-17 11:56 ` Martin Jansa
2018-02-17 12:03 ` Martin Jansa
2018-02-17 13:28 ` Alexander Kanavin
2018-02-17 20:17 ` Seebs
2018-02-18 11:43 ` Martin Jansa
2018-02-18 20:23 ` Martin Jansa
2018-02-19 9:38 ` Alexander Kanavin
2018-02-19 9:27 ` Alexander Kanavin [this message]
2018-02-19 17:55 ` Seebs
2018-02-19 18:37 ` Alexander Kanavin
2018-02-19 19:01 ` Martin Jansa
2018-02-19 19:36 ` Seebs
-- strict thread matches above, loose matches on Subject: below --
2018-03-01 13:53 Alexander Kanavin
2018-03-01 15:06 ` Seebs
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=bb1b003e-9bd3-f438-8ae1-637500d970b5@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=seebs@seebs.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