All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] safe_macros: match oldlib SAFE_CLOSE with docs
Date: Wed, 13 Jul 2016 09:20:01 -0400 (EDT)	[thread overview]
Message-ID: <316514866.4459432.1468416001390.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160713125117.GC2232@rei.scz.novell.com>



----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Wednesday, 13 July, 2016 2:51:17 PM
> Subject: Re: [LTP] [PATCH] safe_macros: match oldlib SAFE_CLOSE with docs
> 
> Hi!
> > > That was the plan, but I didn't get to that today.
> > > 
> > > I was thinking syscalls as well, since most common failure seems
> > > to be errno tests, trying to trigger EBADF, etc.
> > > 
> > > I'll reply once I have results.
> > > 
> > > Regards,
> > > Jan
> > > 
> > > > 
> > > > I do not expect that this will break anything, but there it's a
> > > > possibility.
> > 
> > I ran syscalls (+small selection of other tests) on x86_64, ppc64le
> > and s390x. Only failure was inotify06, but it turned out, that kernel
> > didn't have a patch for this specific failure [1]. It failed with or
> > without oldlib SAFE_CLOSE patch. inotify06 passed with 4.7.0-rc7+.
> 
> Thanks for the testing. Patch is acked.

Pushed.

Regards,
Jan

> 
> --
> Cyril Hrubis
> chrubis@suse.cz
> 

      reply	other threads:[~2016-07-13 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 14:29 [LTP] [PATCH] safe_macros: match oldlib SAFE_CLOSE with docs Jan Stancek
2016-07-12 13:55 ` Cyril Hrubis
2016-07-12 16:10   ` Jan Stancek
2016-07-13 12:52     ` Jan Stancek
2016-07-13 12:51       ` Cyril Hrubis
2016-07-13 13:20         ` Jan Stancek [this message]

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=316514866.4459432.1468416001390.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.