From: Mark Tinguely <tinguely@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: posix_memalign and io_submit do not set errno
Date: Thu, 07 Nov 2013 11:53:35 -0600 [thread overview]
Message-ID: <527BD39F.3020201@sgi.com> (raw)
In-Reply-To: <20131107170045.GA6599@infradead.org>
On 11/07/13 11:00, Christoph Hellwig wrote:
> posix_memalign and io_submit do not set errno, but rather return the
> error respectively the negated error directly.
>
> Found this out while figuring out why 240 reported an impossible error
> from io_submit when run on NFS.
>
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
>
Looks like that took care of all the non-conforming posix_memalign and
io_[submit | cancel | destroy | getevents | setup] calls in xfstests
sources.
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-11-07 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 17:00 [PATCH] xfstests: posix_memalign and io_submit do not set errno Christoph Hellwig
2013-11-07 17:53 ` Mark Tinguely [this message]
2013-11-07 18:13 ` Carlos Maiolino
2013-11-10 1:07 ` Rich Johnston
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=527BD39F.3020201@sgi.com \
--to=tinguely@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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