Add exclusion for /proc/self/.../ns/{net,uts,ipc} files introduced
in kernel 3.0. These files aren't meant to be read and merely
used for getting filedescriptor as a handle to corresponding namespace.
Any file operation on them including read() returns -EINVAL.Signed-off-by: Dmitry Artamonow <[email protected]> --- testcases/kernel/fs/proc/proc01.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) Resending. Previous mail got stuck in moderation queue (2 days already), as I wasn't subscribed when sending (seems that kernel hacking spoiled me, I forgot that not open mailing lists also exist). Sorry, if you'll get it twice in the end. diff --git a/testcases/kernel/fs/proc/proc01.c b/testcases/kernel/fs/proc/proc01.c index ef40a78..0a7695a 100644 --- a/testcases/kernel/fs/proc/proc01.c +++ b/testcases/kernel/fs/proc/proc01.c @@ -94,6 +94,8 @@ const Mapping known_issues[] = { {"read", "/proc/self/task/[0-9]*/mem", EIO}, {"read", "/proc/self/attr/*", EINVAL}, {"read", "/proc/self/task/[0-9]*/attr/*", EINVAL}, + {"read", "/proc/self/ns/*", EINVAL}, + {"read", "/proc/self/task/[0-9]*/ns/*", EINVAL}, {"read", "/proc/ppc64/rtas/error_log", EINVAL}, {"read", "/proc/powerpc/rtas/error_log", EINVAL}, {"read", "/proc/fs/nfsd/unlock_filesystem", EINVAL}, -- 1.7.5.1.300.gc565c ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
