From: Jan Stancek <jstancek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] proc01 hang with 3.10.0-0.rc1/rc2
Date: Fri, 24 May 2013 16:02:14 +0200 [thread overview]
Message-ID: <519F72E6.3090403@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
Hi,
proc01 hangs on read from /proc/self/net/rpc/use-gss-proxy.
I'm attaching a patch if anyone runs rc kernels and is hitting it too,
it's not meant for inclusion to LTP. At least not yet, since the issue
exists only in -rc kernels.
Regards,
Jan
[-- Attachment #2: 0001-proc01-skip-proc-self-net-rpc-use-gss-proxy.patch --]
[-- Type: text/x-patch, Size: 1517 bytes --]
From 77b14e19e319c3b59ef068805abf00d19af008d8 Mon Sep 17 00:00:00 2001
Message-Id: <77b14e19e319c3b59ef068805abf00d19af008d8.1369401766.git.jstancek@redhat.com>
From: Jan Stancek <jstancek@redhat.com>
Date: Fri, 24 May 2013 15:21:18 +0200
Subject: [PATCH] proc01: skip /proc/self/net/rpc/use-gss-proxy
It blocks even with O_NONBLOCK, which causes this test to hang.
This patch also converts WARN to INFO, since there are supposed
to be known failures.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
---
testcases/kernel/fs/proc/proc01.c | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/fs/proc/proc01.c b/testcases/kernel/fs/proc/proc01.c
index f2aa483..c9979ab 100644
--- a/testcases/kernel/fs/proc/proc01.c
+++ b/testcases/kernel/fs/proc/proc01.c
@@ -137,6 +137,8 @@ static const char lsm_should_work[][PATH_MAX] = {
the test while being read. */
static const char error_nonblock[][PATH_MAX] = {
"/proc/xen/xenbus",
+ "/proc/self/net/rpc/use-gss-proxy",
+ "/proc/[0-9]*/net/rpc/use-gss-proxy",
""
};
@@ -363,8 +365,9 @@ static long readproc(const char *obj)
/* Skip files does not honor O_NONBLOCK. */
for (i = 0; error_nonblock[i][0] != '\0'; i++) {
- if (!strcmp(obj, error_nonblock[i])) {
- tst_resm(TWARN, "%s: does not honor "
+ if (!strcmp(obj, error_nonblock[i]) ||
+ !fnmatch(error_nonblock[i], obj, FNM_PATHNAME)) {
+ tst_resm(TINFO, "%s: skip, does not honor "
"O_NONBLOCK", obj);
return 0;
}
--
1.7.1
[-- Attachment #3: Type: text/plain, Size: 421 bytes --]
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
reply other threads:[~2013-05-24 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=519F72E6.3090403@redhat.com \
--to=jstancek@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 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.