From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/madvise06: Exclude other factor that leading to failure
Date: Fri, 5 Aug 2016 08:10:45 -0400 (EDT) [thread overview]
Message-ID: <768798867.1339125.1470399045351.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1470173002-19754-1-git-send-email-yangx.jy@cn.fujitsu.com>
----- Original Message -----
> From: "Xiao Yang" <yangx.jy@cn.fujitsu.com>
> To: ltp@lists.linux.it
> Cc: jstancek@redhat.com, "Xiao Yang" <yangx.jy@cn.fujitsu.com>
> Sent: Tuesday, 2 August, 2016 11:23:22 PM
> Subject: [PATCH] syscalls/madvise06: Exclude other factor that leading to failure
>
> Make sure that madvise(MADV_WILLNEED) supports swap prefetch. We
> can't distinguish between kernel bug and unsupported swap, because
> the same error happens on RHEL6.8GA which madvise(MADV_WILLNEED)
> doesn't support swap prefetch. This feature has been pushed since
> kernel 3.10.0.
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
Pushed with small changes to commit message, I added
commit that introduced this feature for reference.
Regards,
Jan
prev parent reply other threads:[~2016-08-05 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 21:23 [LTP] [PATCH] syscalls/madvise06: Exclude other factor that leading to failure Xiao Yang
2016-08-05 12:10 ` 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=768798867.1339125.1470399045351.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox