Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pseudo: update to latest master
Date: Sat, 17 Feb 2018 15:28:55 +0200	[thread overview]
Message-ID: <bb8be581-a074-b05b-86c6-71e1ee19fdfa@linux.intel.com> (raw)
In-Reply-To: <CA+chaQeNhb=nPaYz3XZdh_ceQopFKJvEq5Ximu83PykTjoHJWA@mail.gmail.com>

On 02/17/2018 02:03 PM, Martin Jansa wrote:
>  > Without this change (pseudo at 'Handle O_TMPFILE more better') things 
> work flawlessly, with epoll enabled.
> 
> Your 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/pseudo-1.9.0 
> is using this change with SRCREV b6a015aa91d7ab84c2f5466f3b5704f501129cbc.
> 
> Does it mean that the change you sent to the ML doesn't work flawlessly 
> and to make it work you need to downgrade SRCREV 
> from b6a015aa91d7ab84c2f5466f3b5704f501129cbc 
> to 23f089f480e04ca1b88df8fe1f46b864fee2a0b8 (while I did upgrade 
> from b6a015aa91d7ab84c2f5466f3b5704f501129cbc 
> to 26e30fa2e1a0fe4e885d7eea3f55d23cd2c3158f after Seebs reply)?
> 
> docker-shr @ ~/projects/pseudo $ git log --oneline yp/master  | head -n 5
> 26e30fa Allow closing client 0
> b6a015a Handle O_TMPFILE more better
> 23f089f Fix openat flag #ifdef typo
> 449c234 Half-undo FASTOP
> d107418 1.9.0

For me, with epoll enabled:

b6a015a works
23f089f and 26e30fa both lock up

Without epoll:

b6a015a works
23f089f produces fd errors
26e30fa wasn't tried.

So I left the poky-contrib branch at the commit where things work, at 
least for me.

Alex


  reply	other threads:[~2018-02-17 13:34 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 [this message]
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
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=bb8be581-a074-b05b-86c6-71e1ee19fdfa@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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