public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ser, Simon" <simon.ser@intel.com>
To: "Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>,
	"Latvala, Petri" <petri.latvala@intel.com>,
	"janusz.krzysztofik@linux.intel.com"
	<janusz.krzysztofik@linux.intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes
Date: Thu, 11 Jul 2019 10:39:51 +0000	[thread overview]
Message-ID: <70b267817cf2f2a7bb1a6dba795026e31ad3893f.camel@intel.com> (raw)
In-Reply-To: <20190711083958.6935-1-janusz.krzysztofik@linux.intel.com>

On Thu, 2019-07-11 at 10:39 +0200, Janusz Krzysztofik wrote:
> If a child process dies for any reason while basic-fence-read or
> basic-fence-mmap subtest is run, the subtest may hang indefinitely on
> read() from a pipe which is supposed to be written to by that child
> (can
> be interrupted though).  Fix it by first closing unused pipe ends on
> both
> parent and child side before using the pipe, as recommended by
> pipe(2)
> manual page.
> 
> Please note that due to the IGT library way of handling signals, now
> the
> subtests may fail with error code 141 (128 + SIGPIPE) and no usual
> DEBUG
> message block on stderr nor FAIL message line on stdout, however some
> meaningful error messages will still be printed on stderr by the
> failing
> child processes.
> 
> v2: resend with Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>     added

You generally don't need to resend a patch just to add a R-b tag.

Do you have IGT commit rights?

> Janusz Krzysztofik (1):
>   tests/prime_vgem: Fix broken handling of interprocess pipes
> 
>  tests/prime_vgem.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-07-11 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11  8:39 [igt-dev] [PATCH i-g-t v2 0/1] tests/prime_vgem: Fix broken handling of interprocess pipes Janusz Krzysztofik
2019-07-11  8:39 ` [igt-dev] [PATCH i-g-t v2 1/1] " Janusz Krzysztofik
2019-07-11 10:39 ` Ser, Simon [this message]
2019-07-11 10:49   ` [igt-dev] [PATCH i-g-t v2 0/1] " Janusz Krzysztofik
2019-07-11 11:17     ` Ser, Simon
2019-07-11 14:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/prime_vgem: Fix broken handling of interprocess pipes (rev2) Patchwork
2019-07-12  5:47 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=70b267817cf2f2a7bb1a6dba795026e31ad3893f.camel@intel.com \
    --to=simon.ser@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janusz.krzysztofik@linux.intel.com \
    --cc=petri.latvala@intel.com \
    /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