From: Jan Stancek <jstancek@redhat.com>
To: Jeffrey Bastian <jbastian@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] proc/proc01.c: ignore stable_secret files
Date: Thu, 9 Jul 2015 11:49:11 -0400 (EDT) [thread overview]
Message-ID: <1003432786.15130300.1436456951899.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150709151457.GT17625@tarantula.localdomain>
----- Original Message -----
> From: "Jeffrey Bastian" <jbastian@redhat.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Thursday, 9 July, 2015 5:14:57 PM
> Subject: Re: [LTP] [PATCH v2] proc/proc01.c: ignore stable_secret files
>
> Linux 4.1.0 introduced a per-NIC IPv6 stable_secret file for RFC7217.
> The stable_secret file for each NIC cannot be read until it is set,
> thus LTP fails like this:
>
> proc01 1 TFAIL : proc01.c:392: read failed:
> /proc/sys/net/ipv6/conf/all/stable_secret: errno=EIO(5): Input/output error
> proc01 2 TFAIL : proc01.c:392: read failed:
> /proc/sys/net/ipv6/conf/default/stable_secret: errno=EIO(5): Input/output
> error
> proc01 3 TFAIL : proc01.c:392: read failed:
> /proc/sys/net/ipv6/conf/eno1/stable_secret: errno=EIO(5): Input/output error
> ...
>
> Add the stable_secret files to the known_issues list in the proc01 test.
>
> TODO: A future test should verify stable_secret functionality.
> ~]# cat /proc/sys/net/ipv6/conf/eno1/stable_secret
> cat: /proc/sys/net/ipv6/conf/eno1/stable_secret: Input/output error
> ~]# echo "ffff:ffff:ffff:ffff:ffff:ffff:255.255.255.255" >
> /proc/sys/net/ipv6/conf/eno1/stable_secret
> ~]# cat /proc/sys/net/ipv6/conf/eno1/stable_secret
> ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
>
> Signed-off-by: Jeffrey Bastian <jbastian@redhat.com>
Pushed.
Thanks,
Jan
> ---
> testcases/kernel/fs/proc/proc01.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/testcases/kernel/fs/proc/proc01.c
> b/testcases/kernel/fs/proc/proc01.c
> index f513110eca0e..2825b51dff95 100644
> --- a/testcases/kernel/fs/proc/proc01.c
> +++ b/testcases/kernel/fs/proc/proc01.c
> @@ -107,6 +107,7 @@ static const struct mapping known_issues[] = {
> {"read", "/proc/fs/nfsd/.getfs", EINVAL},
> {"read", "/proc/fs/nfsd/.getfd", EINVAL},
> {"read", "/proc/self/net/rpc/use-gss-proxy", EAGAIN},
> + {"read", "/proc/sys/net/ipv6/conf/*/stable_secret", EIO},
> {"", "", 0}
> };
>
> --
> 1.9.4
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2015-07-09 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 20:33 [LTP] [PATCH] proc/proc01.c: ignore stable_secret files Jeffrey Bastian
2015-07-09 7:51 ` Jan Stancek
2015-07-09 15:12 ` Jeffrey Bastian
2015-07-09 15:14 ` [LTP] [PATCH v2] " Jeffrey Bastian
2015-07-09 15:49 ` 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=1003432786.15130300.1436456951899.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=jbastian@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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