LTP release
Hi!
As usual we should start preparing for a next release.
As usuall we will have a week or two where we should merge everthing that should go in before the release, then git freeze for another week and finally a release.
So let's start with a list of things that should go in.
For me it would be:
* ptrace08 fix
* if possible the shmctl() rewrite
What else should go in?
Signature · 2 lines
Cyril Hrubis [email protected]
Hi Cyril
Quoted 9 lines
Hi!
As usual we should start preparing for a next release.As usuall we will have a week or two where we should merge everthing that should go in before the release, then git freeze for another week and finally a release.
So let's start with a list of things that should go in.
Quoted 8 lines
For me it would be:
* ptrace08 fix
* if possible the
shmctl()rewriteWhat else should go in?
For me, three patches:
1.syscalls/ioctl_loop07.c?Using LOOP_CONFIGURE to test lo_sizelimit field 2.syscalls/msgrcv07: Add functional test for MSG_COPY flag 3.syscalls/msgrcv03: Add error test for MSG_COPY flag
Best Regards
Yang Xu
Quoted 1 line
Quoted 7 lines · Cyril Hrubis
Hi!
As usual we should start preparing for a next release.As usuall we will have a week or two where we should merge everthing that should go in before the release, then git freeze for another week and finally a release.
Quoted 8 lines
So let's start with a list of things that should go in.
For me it would be:
* ptrace08 fix
* if possible the
shmctl()rewrite
+1 these rewrite looks good, I will finish my test by the end of today.
Quoted 4 lines
What else should go in?
It may be better to fix ioctl_loop01 too.
https://github.com/linux-test-project/ltp/issues/718
And I'd like to add the MAP_GROWSDOWN test too, but I haven't come up with a way to solve the segment fault on s390x.
http://lists.linux.it/pipermail/ltp/2020-August/018416.html
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200908/3490a74a/attachment.htm>
Hi!
Quoted 3 lines
And I'd like to add the
MAP_GROWSDOWNtest too, but I haven't come up with a way to solve the segment fault on s390x.
http://lists.linux.it/pipermail/ltp/2020-August/018416.html
Maybe we end up allocating a mapping that is too close to something else, see:
https://stackoverflow.com/questions/56888725/why-is-map-growsdown-mapping-does-not-grow
I guess that we should make the initial mmap in find_free_range() larger and return and adress that is quaranteed not to have a mapping that is closer than 256 pages in the direction we want to grow.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 10 lines · Cyril Hrubis
Hi!
Quoted 1 line
And I'd like to add the
MAP_GROWSDOWNtest too, but I haven't come upwith
Quoted 2 lines
a way to solve the segment fault on s390x.
http://lists.linux.it/pipermail/ltp/2020-August/018416.htmlMaybe we end up allocating a mapping that is too close to something else, see:
Quoted 6 lines
https://stackoverflow.com/questions/56888725/why-is-map-growsdown-mapping-does-not-grow
I guess that we should make the initial mmap in
find_free_range()larger and return and adress that is quaranteed not to have a mapping that is closer than 256 pages in the direction we want to grow.
Sounds reasonable. I tried to reserve more space for the mapping grows, and that works for me:).
static void *find_free_range(size_t size)
{
void *mem;
/*
* To avoid the mapping grows to within a page of the high end of
* the next lower mapping, which might result in a SIGSEGV signal.
* Here reserve twifold memory spaces for growing, especially for s390x.
*/
mem = SAFE_MMAP(NULL, size * 2, PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
SAFE_MUNMAP(mem, size * 2);
return mem;
}Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200909/6a41a5be/attachment.htm>
Quoted 16 lines · Li Wang
Quoted 12 lines · Cyril Hrubis
Hi!
Quoted 1 line
And I'd like to add the
MAP_GROWSDOWNtest too, but I haven't come upwith
Quoted 2 lines
a way to solve the segment fault on s390x.
http://lists.linux.it/pipermail/ltp/2020-August/018416.htmlMaybe we end up allocating a mapping that is too close to something else, see:
https://stackoverflow.com/questions/56888725/why-is-map-growsdown-mapping-does-not-grow
Quoted 8 lines
Quoted 4 lines
I guess that we should make the initial mmap in
find_free_range()larger and return and adress that is quaranteed not to have a mapping that is closer than 256 pages in the direction we want to grow.Sounds reasonable. I tried to reserve more space for the mapping grows, and that works for me:).
To precisely, we could reserve 256 pages size at the end of the free-range memory to let the stack keep away from a preceding mapping in its growing then.
(my only concern is the stack_guard_gap can be changed via kernel command line, but I assume that happen rarely, so here use the default 256 pages)
If there is no objection, I'd make these changes in patch V4.
--------
static void *find_free_range(size_t size)
{
void *mem;
long stack_guard_gap = 256 * getpageszie();
/*
* Since the newer kernel does not allow a MAP_GROWSDOWN mapping to grow
* closer than stack_guard_gap pages away from a preceding mapping.
* The guard then ensures that the next-highest mapped page remains more
* than stack_guard_gap below the lowest stack address, and if not then
* it will trigger a segfault. So, here let's reserve 256 pages memory
* spacing for stack growing safely.
*/
mem = SAFE_MMAP(NULL, size + stack_guard_gap, PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
SAFE_MUNMAP(mem, size + stack_guard_gap);
return mem;
}
static void split_unmapped_plus_stack(void *start, size_t size) {
/* start start + size
* +---------------------+----------------------+-----------+
* + unmapped | mapped | 256 pages |
* +---------------------+----------------------+-----------+
* stack
*/
stack = SAFE_MMAP(start + size, size, PROT_READ | PROT_WRITE,
MAP_FIXED | MAP_PRIVATE | MAP_ANONYMOUS |MAP_GROWSDOWN,
-1, 0); }
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200909/47ddab4d/attachment-0001.htm>
Hi!
Quoted 34 lines
Quoted 3 lines
Sounds reasonable. I tried to reserve more space for the mapping grows, and that works for me:).
To precisely, we could reserve 256 pages size at the end of the free-range memory to let the stack keep away from a preceding mapping in its growing then.
(my only concern is thestack_guard_gapcan be changed via kernel command line, but I assume that happen rarely, so here use the default 256 pages)If there is no objection, I'd make these changes in patch V4.
--------
static void *find_free_range(size_t size)
{
void *mem;
longstack_guard_gap= 256 *getpageszie();/*
* Since the newer kernel does not allow aMAP_GROWSDOWNmapping to grow
* closer thanstack_guard_gappages away from a preceding mapping.
* The guard then ensures that the next-highest mapped page remains more
* thanstack_guard_gapbelow the lowest stack address, and if not then
* it will trigger a segfault. So, here let's reserve 256 pages memory
* spacing for stack growing safely.
*/
mem = SAFE_MMAP(NULL, size +stack_guard_gap,PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0);
SAFE_MUNMAP(mem, size + stack_guard_gap);return mem;
}
Quoted 8 lines
static void
split_unmapped_plus_stack(void *start, size_t size){
/* start start + size
* +---------------------+----------------------+-----------+
* + unmapped | mapped | 256 pages |
* +---------------------+----------------------+-----------+
* stack
*/
Shouldn't the 256 pages follow the unmapped part?
If I'm not mistaken if stack grows down the address decreases with stack allocations, so it should be as:
| 256 pages | unmapped | mapped |
That would also mean that we should map the stack at address start + total_size - size if I'm not mistaken. I guess that we can put all the mess into a single function as well and have just allocate_stack() that will find a suitable address, mmap the stack together, splitting this into two functions is unnecessary confusing.
Quoted 5 lines
stack = SAFE_MMAP(start + size, size,
PROT_READ|PROT_WRITE,
MAP_FIXED|MAP_PRIVATE|MAP_ANONYMOUS|MAP_GROWSDOWN,-1, 0); }
Also I would like to get rid of the -fno-optimize-sibling-calls in the Makefile, this makes the test a bit fragile and less portable.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi!
Quoted 2 lines
Also I would like to get rid of the -fno-optimize-sibling-calls in the
Makefile, this makes the test a bit fragile and less portable.
What about this code:
#include <stdint.h>
#include <stdio.h>
static intptr_t addr_func(void) __attribute__((noinline));
static intptr_t addr_func(void)
{
int a;
return (intptr_t)&a;
}/*
* Returns negative number if stack grows down, possitive if stack grows up */
static int stack_dir(void)
{
intptr_t addr = addr_func();
printf("%p %p\n", &addr, (void*)addr);
return addr - (intptr_t)&addr;
}int main(void)
{
printf("%i\n", stack_dir());
return 0;
}Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 4 lines · Cyril Hrubis
Hi!
Quoted 2 lines
Also I would like to get rid of the -fno-optimize-sibling-calls in the
Makefile, this makes the test a bit fragile and less portable.
I'm not very sure, let me think/check a while.
Quoted 9 lines
/*
* Returns negative number if stack grows down, possitive if stack grows up */
static intstack_dir(void){ intptr_t addr = addr_func(); printf("%p %p\n", &addr, (void*)addr);
This method may be doable, but the second %p print (nil), I don't why.
# ./test 0x3ffe70feb48 (nil) 418387128
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200910/9cc9af0d/attachment.htm>
Quoted 11 lines · Li Wang
Quoted 4 lines · Cyril Hrubis
Hi!
Quoted 2 lines
Also I would like to get rid of the -fno-optimize-sibling-calls in the
Makefile, this makes the test a bit fragile and less portable.I'm not very sure, let me think/check a while.
From the document, it could also help prevents optimization purposes. I think we can have a try, if no more issues, that will be great.
Quoted 10 lines
Quoted 10 lines
/*
* Returns negative number if stack grows down, possitive if stack grows
up
*/
static intstack_dir(void){ intptr_t addr = addr_func();
Quoted 5 lines
Quoted 2 lines
printf("%p %p\n", &addr, (void*)addr);This method may be doable, but the second %p print (nil), I don't why.
The reason seems that the local variable is revoked after the function is calling, so we get NULL of the local variable address. It works as we expected when introducing a global pointer to save and return the '&a'.
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200910/74f43ed2/attachment-0001.htm>
Hi Cyril:
Can we merge the uart device driver testcase and the device-discover framework ? So that we can continue write other device driver case in LTP.
I am looking forward contribute to ltp on the driver test .
https://patchwork.ozlabs.org/project/ltp/list/?series=185240
https://patchwork.ozlabs.org/project/ltp/list/?series=195151
Li Wang <[email protected]> ?2020?9?10??? ??5:23???
Quoted 46 lines · Li Wang
Quoted 11 lines · Cyril Hrubis
Quoted 4 lines
Hi!
Quoted 2 lines
Also I would like to get rid of the -fno-optimize-sibling-calls in the
Makefile, this makes the test a bit fragile and less portable.I'm not very sure, let me think/check a while.
From the document, it could also help prevents optimization purposes. I think we can have a try, if no more issues, that will be great.
Quoted 10 lines
Quoted 10 lines
/*
* Returns negative number if stack grows down, possitive if stack grows up */
static intstack_dir(void){ intptr_t addr = addr_func();Quoted 4 lines
Quoted 1 line
printf("%p %p\n", &addr, (void*)addr);This method may be doable, but the second %p print (nil), I don't why.
The reason seems that the local variable is revoked after the function is calling, so we get NULL of the local variable address. It works as we expected when introducing a global pointer to save and return the '&a'.
--
Regards,
Li Wang--
Mailing list info: https://lists.linux.it/listinfo/ltp
Hi!
Quoted 2 lines
Can we merge the uart device driver testcase and the device-discover framework ???
Can we please postpone it a little bit again? I've been talking to Tim Bird recenlty and he is interesting in helping to shape the interface so better that it fits into existing hardware labs.
Quoted 2 lines
So that we can continue write other device driver case in LTP. I am looking forward contribute to ltp on the driver test.
That's great looking forward to your contributions.
Also I'm sorry that I haven't been able to move this forward, I will try to speed things up after we are done with the LTP release. Is that fine with you?
Signature · 2 lines
Cyril Hrubis [email protected]
Bird
Quoted 10 lines
-----Original Message-----
From: Cyril HrubisHi!
Quoted 2 lines
Can we merge the uart device driver testcase and the device-discover framework ???
Can we please postpone it a little bit again? I've been talking to Tim Bird recenlty and he is interesting in helping to shape the interface so better that it fits into existing hardware labs.
I'm very interested in this work, and how to integrate it with external test frameworks that manage lab equipment (and may need to communicate test parameters to tests).
I'm not sure the best way to proceed. I reviewed the device-discovery code on patchworks, but I'm not sure I understand the anticipated flow of control between the LTP test, the device discovery part, and the test framework.
I know you're busy with the LTP release, so I'm not sure this is the best time to open up a big thread asking a lot of questions about device discovery or describing my own proposal for this - to work towards harmonizing the two.
But I'm keen on following up on this in the short term (next 4 weeks or so). I'm giving a talk at Open Source Summit Europe the end of October, where I'll be talking about lab management APIs, and this dovetails into that work.
Let me know when would be a good time to try to hash this out.
-- Tim
Thanks Bird and Cyril, I will be waiting for work to start this work as soon as your hava the time
to guide me
If there have anything to do before it, just tell me.
Bird, Tim <[email protected]> ?2020?9?15??? ??1:51???
Quoted 33 lines
Quoted 11 lines
-----Original Message-----
From: Cyril HrubisHi!
Quoted 2 lines
Can we merge the uart device driver testcase and the device-discover framework ???
Can we please postpone it a little bit again? I've been talking to Tim Bird recenlty and he is interesting in helping to shape the interface so better that it fits into existing hardware labs.
I'm very interested in this work, and how to integrate it with external test frameworks that manage lab equipment (and may need to communicate test parameters to tests).
I'm not sure the best way to proceed. I reviewed the device-discovery code on patchworks, but I'm not sure I understand the anticipated flow of control between the LTP test, the device discovery part, and the test framework.
I know you're busy with the LTP release, so I'm not sure this is the best time to open up a big thread asking a lot of questions about device discovery or describing my own proposal for this - to work towards harmonizing the two.
But I'm keen on following up on this in the short term (next 4 weeks or so). I'm giving a talk at Open Source Summit Europe the end of October, where I'll be talking about lab management APIs, and this dovetails into that work.
Let me know when would be a good time to try to hash this out.
-- Tim
Hi!
Quoted 17 lines
Quoted 3 lines
Can we please postpone it a little bit again? I've been talking to Tim Bird recenlty and he is interesting in helping to shape the interface so better that it fits into existing hardware labs.
I'm very interested in this work, and how to integrate it with external test frameworks that manage lab equipment (and may need to communicate test parameters to tests).
I'm not sure the best way to proceed. I reviewed the device-discovery code on patchworks, but I'm not sure I understand the anticipated flow of control between the LTP test, the device discovery part, and the test framework.
I know you're busy with the LTP release, so I'm not sure this is the best time to open up a big thread asking a lot of questions about device discovery or describing my own proposal for this - to work towards harmonizing the two.
Quoted 6 lines
But I'm keen on following up on this in the short term (next 4 weeks or so). I'm giving a talk at Open Source Summit Europe the end of October, where I'll be talking about lab management APIs, and this dovetails into that work.
Let me know when would be a good time to try to hash this out.
I guess that I can allocate some time between pre-release testing that will happen soon after we freeze the git.
Let me just dump what I have in mind, I guess that the proof-of-concept and the potential directions will be easier to understand with a few hints.
Each hardware type has a specific name that identifies it, in a case of serial port the test requires "UART_RX" and "UART_TX" which defines an UART loop. In a case of i2c EEPROM that would probably be "I2C_EEPROM_ADDR" and "I2C_EEPROM_BUS" etc. This is what is going to be used to query the lab mamagenent software and the reply would be a list of suitable devices along with their capabilities. In a case of UART it may be declaring supported speeds, if hardware flow is supported etc. In a case of EEPROM it will add a device size along with the bus and address.
The interface to the lab mamagement software was choosen to be an executable, in the simplest cases it could be just a shell script that enumerates all unused serial ports, in more complex cases it may connect to a REST API on a lab management server and get the reply from there.
Once the hardware has been discovered the test will iterate over the list of suitable devices and do a testrun for each of these. But since some hardware needs to be possibly reserved/freed and reconfigured there has to be hooks for that, which would be probably executables again.
The proof-of-concept that I wrote was quite simple, it includes a code in the LTP test library that can loop over a list of available devices returned by the discovery script and a sample empty script where the hardware discovery code should be put into along with a UART test that uses all that newly added functionality. There are a few open problems with the current code though, the parameters are passed to the test via shell variables, which is not going to work well for a more structured data. Maybe the discovery script should return JSON which would be translated by the shell library into a command line parameters.
Something as:
{
"uart_tx": "/dev/ttyS0",
"uart_rx": "/dev/ttyS1",
"speeds": [
"9600",
"19200", ],
"hwflow": [
true,
false
],
"reconfigure": "/usr/bin/lab_reconfigure --connect-uart /dev/ttyS0 /dev/ttyS1"
},
Which would result in running:
/usr/bin/lab_reconfigure --connect-uart /dev/ttyS0 /dev/ttyS1 /opt/ltp/testcases/bin/uart01 --uart_tx "/dev/ttyS0" --uart_rx "/dev/ttyS1" --speed 9600 --hwflow true /opt/ltp/testcases/bin/uart01 --uart_tx "/dev/ttyS0" --uart_rx "/dev/ttyS1" --speed 9600 --hwflow false /opt/ltp/testcases/bin/uart01 --uart_tx "/dev/ttyS0" --uart_rx "/dev/ttyS1" --speed 19200 --hwflow true /opt/ltp/testcases/bin/uart01 --uart_tx "/dev/ttyS0" --uart_rx "/dev/ttyS1" --speed 19200 --hwflow false
And the test would only need to declare that it requires "UART_LOOP" or something like that.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 10 lines · Cyril Hrubis
...
Quoted 8 lines
static void
split_unmapped_plus_stack(void *start, size_t size){
/* start start + size
* +---------------------+----------------------+-----------+
* + unmapped | mapped | 256 pages |
* +---------------------+----------------------+-----------+
* stack
*/
Quoted 2 lines
Shouldn't the 256 pages follow the unmapped part?
Yes, you're right. I made a mistake on draw that. Will fix in V4.
Quoted 4 lines
If I'm not mistaken if stack grows down the address decreases with stack allocations, so it should be as:
Quoted 9 lines
| 256 pages | unmapped | mapped |
That would also mean that we should map the stack at address start +
total_size- size if I'm not mistaken. I guess that we can put all the mess into a single function as well and have justallocate_stack()that will find a suitable address, mmap the stack together, splitting this into two functions is unnecessary confusing.
Good point, it makes sense to me.
Quoted 15 lines
Quoted 6 lines
stack = SAFE_MMAP(start + size, size,
PROT_READ|PROT_WRITE,
MAP_FIXED|MAP_PRIVATE|MAP_ANONYMOUS|MAP_GROWSDOWN,-1, 0); }Also I would like to get rid of the -fno-optimize-sibling-calls in the
Makefile, this makes the test a bit fragile and less portable.--
Cyril Hrubis
[email protected]
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200910/52c12c26/attachment.htm>
Hi Cyril,
Quoted 1 line
As usual we should start preparing for a next release.
...
Quoted 1 line
What else should go in?
I haven't done review of Amir's fanotify tests for v5.9, but on first look they look ok
https://patchwork.ozlabs.org/project/ltp/list/?series=200606
How about Richie's Wrapper for Syzkaller reproducers?
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
I wanted to post docparser patch in next few days. But that will be probably too late for including in this release.
Kind regards,
Petr
Hi,
Quoted 1 line
What else should go in?
How about removing runtest/quickhit?
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
And I'll try to to send next version of 'make check' soon.
Kind regards,
Petr
Hi!
Quoted 3 lines
Quoted 1 line
What else should go in?
How about removing runtest/quickhit?
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/
I guess that we can do that if we replace it with something Tim can use for infrastructure tests.
Tim what are your expectation from such runtest file? How many tests should be in?
Signature · 2 lines
Cyril Hrubis [email protected]
Bird
Quoted 7 lines
-----Original Message-----
From: Cyril Hrubis <[email protected]>Hi!
Quoted 1 line
Quoted 1 line
What else should go in?
Quoted 8 lines
Quoted 2 lines
How about removing runtest/quickhit?
https://patchwork.ozlabs.org/project/ltp/patch/[email protected]/I guess that we can do that if we replace it with something Tim can use for infrastructure tests.
Tim what are your expectation from such runtest file? How many tests should be in?
I don't think that it should be very many. Otherwise, people will get the idea that it is useful for actual device testing. ;-)
The current 'quickhit' runtest file has 107 tests. With the exception of
qmm01 (which calls mmap001 with '-n 1') and a bunch of tests that do sub-tests of symlink01 (12 of them), the remaining test definitions
just consist of the test name and the test executable (with the same names).
I only see binary programs - no tests using shell scripts. So there's really not much variety here.
Apparently a pipe is allowed in the command invocation line for a test, but there's only one example of this in all of the runtests, in syscalls:
splice02 seq 1 2000 | splice02
Really, as an infrastructure test, I only need to run a few testcases to validate that Fuego's plumbing around runltp (and ltp-pan) works properly. And it would be nice if the run was very short, so I could do the check quickly.
Do you want me to create a runtest for a framework/LTP integration test, by picking a few different "representative" tests, as a replacement for quickhit?
IMHO, the selected tests should behave the same on all possible systems, to avoid getting results that are inconsistent due to the system under test, rather than a problem with the integration between the framework and LTP.
Should I add some outlier cases:
- something that times out
- something that always fails
- tests that return TBROK, TCONF, TWARN, etc.
- something where the command doesn't exist
This would be helpful for checking that my parsing for different results works.
Do you have a preferred name for the runtest file? My proposal, just off the top of my head, is: "ltp-selftest-quick", but I'm open to other suggestions.
I'm also open to suggestions for possible tests. I'd like a shell script command to add to the list of binary programs. Here is what I've chosen so far:
access01 access01
chdir01 chdir01
fork01 fork01
time01 time01
wait02 wait02
write01 write01
symlink01 symlink01
stat04 symlink01 -T stat04
utime01A symlink01 -T utime01
rename01A symlink01 -T rename01
splice02 seq 1 20 | splice02
This takes about 5 seconds on one of my test machines.
-- Tim
P.S. Maybe, if you're moving away from runltp and ltp-pan, it's a little late to be adding some selftests to make sure they work correctly. But Fuego is using them. I don't know what other frameworks use when they invoke LTP to perform tests.
P.P.S How come some tests produce TPASS and some produce just PASS?
Hi Tim, Cyril,
Quoted 5 lines
I'm also open to suggestions for possible tests. I'd like a shell script command to add to the list of binary programs. Here is what I've chosen so far:
access01 access01
chdir01 chdir01
fork01 fork01
Quoted 8 lines
time01 time01
wait02 wait02
write01 write01
symlink01 symlink01
stat04 symlink01 -T stat04
utime01A symlink01 -T utime01
rename01A symlink01 -T rename01
splice02 seq 1 20 | splice02
Could we please add at least one network test program?
e.g. route tests with netlink also uses shell API and it's really quick (real time 0m0,687s):
route6-change-netlink-dst route-change-netlink-dst.sh -6
Quoted 1 line
This takes about 5 seconds on one of my test machines.
+1
Quoted 8 lines
-- Tim
P.S. Maybe, if you're moving away from runltp and ltp-pan, it's a little late to be adding some selftests to make sure they work correctly. But Fuego is using them. I don't know what other frameworks use when they invoke LTP to perform tests.
P.P.SHow come some tests produce TPASS and some produce just PASS?
Legacy C API and shell API (both legacy and new) add T (i.e. TPASS), new C API don't add it (i.e. PASS). It's a minor detail we could fix that.
Kind regards,
Petr
Hi!
Quoted 10 lines
I don't think that it should be very many. Otherwise, people will get the idea that it is useful for actual device testing. ;-)
The current 'quickhit' runtest file has 107 tests. With the exception of
qmm01 (which calls mmap001 with '-n 1') and a bunch of tests that do sub-tests of symlink01 (12 of them), the remaining test definitions
just consist of the test name and the test executable (with the same names).
I only see binary programs - no tests using shell scripts. So there's really not much variety here.
Quoted 3 lines
Apparently a pipe is allowed in the command invocation line for a test, but there's only one example of this in all of the runtests, in syscalls:
splice02 seq 1 2000 | splice02
Actually the logic in LTP pan is:
* If the command part is single string the test is executed by execve()
* Otherwise it's passed as a command to run to /bin/sh
I'm not sure it we would want to retain that behaivor for a future though.
Quoted 17 lines
Really, as an infrastructure test, I only need to run a few testcases to validate that Fuego's plumbing around runltp (and ltp-pan) works properly. And it would be nice if the run was very short, so I could do the check quickly.
Do you want me to create a runtest for a framework/LTP integration test, by picking a few different "representative" tests, as a replacement for quickhit?
IMHO, the selected tests should behave the same on all possible systems, to avoid getting results that are inconsistent due to the system under test, rather than a problem with the integration between the framework and LTP.
Should I add some outlier cases:
- something that times out
- something that always fails
- tests that return TBROK, TCONF, TWARN, etc.
- something where the command doesn't exist
Quoted 4 lines
This would be helpful for checking that my parsing for different results works.
Do you have a preferred name for the runtest file? My proposal, just off the top of my head, is: "ltp-selftest-quick", but I'm open to other suggestions.
Maybe we should call it smoketest, but I'm okay selftest as well.
Quoted 14 lines
I'm also open to suggestions for possible tests. I'd like a shell script command to add to the list of binary programs. Here is what I've chosen so far:
access01 access01
chdir01 chdir01
fork01 fork01
time01 time01
wait02 wait02
write01 write01
symlink01 symlink01
stat04 symlink01 -T stat04
utime01A symlink01 -T utime01
rename01A symlink01 -T rename01
splice02 seq 1 20 | splice02
Quoted 1 line
This takes about 5 seconds on one of my test machines.
So I will add a network test to the set and push that before a patch that removes quickhit.
It would be nice to have the outliners, but that is a bit more complicated change, so I would like to add these after a release, is that okay?
Quoted 4 lines
P.S. Maybe, if you're moving away from runltp and ltp-pan, it's a little late to be adding some selftests to make sure they work correctly. But Fuego is using them. I don't know what other frameworks use when they invoke LTP to perform tests.
I do expect that we will have ltp-pan included for compatibility reasons at least for a year or two once the replacement would be in place anyways, so having a smoketest wouldn't harm at all.
Signature · 2 lines
Cyril Hrubis [email protected]
Bird
Just to finish answering questions...
Quoted 7 lines
-----Original Message-----
From: Cyril Hrubis <[email protected]>Quoted 2 lines
Do you have a preferred name for the runtest file? My proposal, just off the top of my head, is: "ltp-selftest-quick", but I'm open to other suggestions.
Maybe we should call it smoketest, but I'm okay selftest as well.
I'm fine with "smoketest".
...
Quoted 9 lines
Quoted 2 lines
This takes about 5 seconds on one of my test machines.
So I will add a network test to the set and push that before a patch that removes quickhit.
It would be nice to have the outliners, but that is a bit more complicated change, so I would like to add these after a release, is that okay?
Yes. I think that's actually better. I think a simple change now is good. I'd like to think some more about whether it would be good to add things that misbehave to smoketest, or if they should be put into a separate selftest group. My inclination is that a smoketest should really just be a super-quick check that should work unless something fundamental is broken, while selftest should try as many things as possible, including weird stuff and corner cases, to actually test specific features of runtest handling.
I'm satisfied with the current smoketest content.
Quoted 9 lines
Quoted 5 lines
P.S. Maybe, if you're moving away from runltp and ltp-pan, it's a little late to be adding some selftests to make sure they work correctly. But Fuego is using them. I don't know what other frameworks use when they invoke LTP to perform tests.I do expect that we will have ltp-pan included for compatibility reasons at least for a year or two once the replacement would be in place anyways, so having a smoketest wouldn't harm at all.
Sounds good.
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 7 lines · Cyril Hrubis
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.
We still got this persistent fail on some kernels(RHEL8, kernel-v5.9-rc4):
---
send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11)
---
fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
---
recvmmsg01.c:86:9: error: request for member ?type? in something not a structure or union
timeout.type = tv->ts_type;
Otherwise, the latest LTP test good from my side(RHEL8, mainline-kernel).
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200923/2ea96afc/attachment.htm>
CC' people who touched the patches maybe give a hand.
Quoted 45 lines · Li Wang
Quoted 7 lines · Cyril Hrubis
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.We still got this persistent fail on some
kernels(RHEL8, kernel-v5.9-rc4):---
send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11)---
fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12---
recvmmsg01.c:86:9: error: request for member ?type? in something not a structure or union
timeout.type =tv->ts_type;Otherwise, the latest LTP test good from my
side(RHEL8, mainline-kernel).--
Regards,
Li Wang
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200923/e25ccedb/attachment-0001.htm>
Hi Li,
Quoted 1 line
CC' people who touched the patches maybe give a hand.
+1
Quoted 12 lines · Li Wang
Quoted 9 lines · Cyril Hrubis
Quoted 7 lines
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.
Quoted 7 lines
Quoted 7 lines
We still got this persistent fail on some
kernels(RHEL8, kernel-v5.9-rc4):---
send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11)
This is working on openSUSE kernel 5.9.0-rc3. I haven't checked whether there are some special patches or whether there is a regression in rc4.
Quoted 5 lines
Quoted 5 lines
---
fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
Quoted 8 lines
Quoted 8 lines
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
Again, working on openSUSE kernel 5.9.0-rc3.
Quoted 4 lines
Quoted 4 lines
---
recvmmsg01.c:86:9: error: request for member ?type? in something not a structure or union
timeout.type =tv->ts_type;
Yes, 135af8ededd4d74d32f3322801fbab1f732a259a added in recvmmsg01 broke build:
https://travis-ci.org/github/linux-test-project/ltp/builds/729394877
(this build is for sendto03 - next commit, but that's ok)
Having a look into it.
Quoted 1 line
Quoted 1 line
Otherwise, the latest LTP test good from my
side(RHEL8, mainline-kernel).
Kind regards,
Petr
? 2020/9/23 17:29, Petr Vorel ??:
Quoted 42 lines
Hi Li,
Quoted 1 line
CC' people who touched the patches maybe give a hand.
+1
Quoted 9 lines · Li Wang
Quoted 7 lines · Cyril Hrubis
Quoted 6 lines
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.Quoted 6 lines
Quoted 6 lines
We still got this persistent fail on some
kernels(RHEL8, kernel-v5.9-rc4):
---
send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11)This is working on openSUSE kernel 5.9.0-rc3. I haven't checked whether there are some special patches or whether there is a regression in rc4.
Quoted 5 lines
Quoted 5 lines
---
fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12Quoted 8 lines
Quoted 8 lines
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12Again, working on openSUSE kernel 5.9.0-rc3.
Quoted 4 lines
Quoted 4 lines
---
recvmmsg01.c:86:9: error: request for member ?type? in something not a structure or union
timeout.type =tv->ts_type;
Quoted 5 lines
Yes,
135af8ededd4d74d32f3322801fbab1f732a259aadded in recvmmsg01 broke build:
https://travis-ci.org/github/linux-test-project/ltp/builds/729394877
(this build is for sendto03 - next commit, but that's ok)Having a look into it.
Hi Petr, Li
I sent a patch to fix the compiler error after a quick look:
http://lists.linux.it/pipermail/ltp/2020-September/019060.html
Thanks,
Xiao Yang
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Otherwise, the latest LTP test good from my
side(RHEL8, mainline-kernel).Kind regards,
Petr
? 2020/9/23 14:58, Li Wang ??:
Quoted 36 lines
CC' people who touched the patches maybe give a hand.
On Wed, Sep 23, 2020 at 2:50 PM Li Wang <[email protected] <mailto:[email protected]>> wrote:
On Wed, Sep 23, 2020 at 2:20 AM Cyril Hrubis <[email protected] <mailto:[email protected]>> wrote: Hi! As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find. We still got this persistent fail on some kernels(RHEL8, kernel-v5.9-rc4): --- send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL: recv() error: EAGAIN/EWOULDBLOCK (11) --- fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12 fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
Quoted 9 lines
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020
(expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020
(expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020
(expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020
(expected 1000) pid=95067 fd=12Hi Li,
I didn't reproduce the issue about fanotify10 on the lastest kernel(kernel-v5.9-rc6+):
-------------------------
[root@Fedora-30 fanotify]# ./fanotify10
tst_device.c:88: TINFO: Found free device 0 '/dev/loop0' tst_mkfs.c:89: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.46-WIP (20-Mar-2020)
tst_test.c:1248: TINFO: Timeout per run is 0h 05m 00s fanotify10.c:452: TINFO: Test #0: ignore mount events created on a specific file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1981 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1981 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1981 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #1: ignore exec mount events created on a specific file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1983 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1983 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1983 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1000 pid=1983 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1000 pid=1983 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1000 pid=1983 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1000 pid=1983 fd=4294967295
fanotify10.c:452: TINFO: Test #2: don't ignore mount events created on another file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=1984 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=1984 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=1984 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=1984 fd=4294967295
fanotify10.c:452: TINFO: Test #3: don't ignore exec mount events created on another file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1020 pid=1985 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1020 pid=1985 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1020 pid=1985 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1020 pid=1985 fd=4294967295
fanotify10.c:452: TINFO: Test #4: ignore inode events created on a specific mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1986 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1986 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1986 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_INODE and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:452: TINFO: Test #5: ignore exec inode events created on a specific mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1987 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1987 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1987 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1000 pid=1987 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1000 pid=1987 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1000 pid=1987 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1000 pid=1987 fd=4294967295
fanotify10.c:452: TINFO: Test #6: don't ignore inode events created on another mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=1988 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=1988 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=1988 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=1988 fd=4294967295
fanotify10.c:452: TINFO: Test #7: don't ignore exec inode events created on another mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1020 pid=1989 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1020 pid=1989 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1020 pid=1989 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1020 pid=1989 fd=4294967295
fanotify10.c:452: TINFO: Test #8: ignore fs events created on a specific file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1990 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1990 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1990 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #9: ignore exec fs events created on a specific file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1991 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1991 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1991 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1000 pid=1991 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1000 pid=1991 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1000 pid=1991 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1000 pid=1991 fd=4294967295
fanotify10.c:452: TINFO: Test #10: don't ignore mount events created on another file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=1992 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=1992 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=1992 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=1992 fd=4294967295
fanotify10.c:452: TINFO: Test #11: don't ignore exec mount events created on another file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1020 pid=1993 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1020 pid=1993 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1020 pid=1993 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1020 pid=1993 fd=4294967295
fanotify10.c:452: TINFO: Test #12: ignore fs events created on a specific mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1994 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1994 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1994 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_MOUNT ignore mask got no event
fanotify10.c:452: TINFO: Test #13: ignore exec fs events created on a specific mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1995 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1995 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1995 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1000 pid=1995 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1000 pid=1995 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1000 pid=1995 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1000 pid=1995 fd=4294967295
fanotify10.c:452: TINFO: Test #14: don't ignore fs events created on another mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=1996 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=1996 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=1996 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=1996 fd=4294967295
fanotify10.c:452: TINFO: Test #15: don't ignore exec fs events created on another mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1020 pid=1997 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1020 pid=1997 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1020 pid=1997 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1020 pid=1997 fd=4294967295
fanotify10.c:452: TINFO: Test #16: ignore child exec events created on a specific mount point
fanotify10.c:411: TPASS: group 0 (8) got event: mask 1020 pid=1998 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 1020 pid=1998 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 1020 pid=1998 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 1000 pid=1998 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 1000 pid=1998 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 1000 pid=1998 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 1000 pid=1998 fd=4294967295
fanotify10.c:452: TINFO: Test #17: ignore events on children of directory created on a specific file
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=1999 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=1999 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=1999 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #18: ignore events on file created inside a parent watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2000 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2000 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2000 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_INODE and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #19: don't ignore events on file created inside a parent not watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=2001 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=2001 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=2001 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=2001 fd=4294967295
fanotify10.c:452: TINFO: Test #20: ignore mount events created inside a parent watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2002 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2002 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2002 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_MOUNT and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #21: don't ignore mount events created inside a parent not watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=2003 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=2003 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=2003 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=2003 fd=4294967295
fanotify10.c:452: TINFO: Test #22: ignore fs events created inside a parent watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2004 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2004 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2004 fd=15 fanotify10.c:523: TPASS: group 0 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (4) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (0) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 0 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 1 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:523: TPASS: group 2 (e00) with FAN_MARK_FILESYSTEM and FAN_MARK_INODE ignore mask got no event
fanotify10.c:452: TINFO: Test #23: don't ignore fs events created inside a parent not watching children
fanotify10.c:411: TPASS: group 0 (8) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 1 (8) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 2 (8) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 0 (4) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 1 (4) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 2 (4) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 0 (0) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 1 (0) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 2 (0) got event: mask 20 pid=2005 fd=15 fanotify10.c:411: TPASS: group 0 (e00) got event: mask 20 pid=2005 fd=4294967295
fanotify10.c:411: TPASS: group 1 (e00) got event: mask 20 pid=2005 fd=4294967295
fanotify10.c:411: TPASS: group 2 (e00) got event: mask 20 pid=2005 fd=4294967295
Summary:
passed 288 failed 0 skipped 0
warnings 0
-------------------------
Is the issue fixed recently? :-)
Best Regards,
Xiao Yang
Quoted 7 lines
---
recvmmsg01.c:86:9: error: request for member ?type? in something not a structure or union
timeout.type =tv->ts_type;
Quoted 15 lines
Otherwise, the latest LTP test good from my
side(RHEL8, mainline-kernel).--
Regards,
Li WangSignature · 2 lines
Regards, Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200923/dc403799/attachment-0001.htm>
Quoted 41 lines · Xiao Yang
? 2020/9/23 14:58, Li Wang ??:
CC' people who touched the patches maybe give a hand.
Quoted 20 lines · Li Wang
Quoted 7 lines · Cyril Hrubis
Hi!
As far as I can tell I've pushed the last patch that should have been in the release just now. With that we should have a week worth of pre-release testing since we are aiming for a release at the end of the September. If you haven't tried LTP git HEAD yet, please do so now and report any problems you find.We still got this persistent fail on some
kernels(RHEL8, kernel-v5.9-rc4):---
send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11) send02.c:86: FAIL:recv()error: EAGAIN/EWOULDBLOCK (11)Quoted 14 lines
---
fanotify10.c:404: TFAIL: group 0 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (4) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 0 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 1 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
fanotify10.c:404: TFAIL: group 2 (0) got event: mask 1020 (expected 1000) pid=95067 fd=12
Quoted 5 lines
Hi Li,
I didn't reproduce the issue about fanotify10 on the lastest kernel(kernel-v5.9-rc6+):
Sorry for the unclear description.
The fanotify10 failed on RHEL8, I?m now trying to see if some kernel patch missing.
And send02 failed on kernel-v5.9-rc4.
Signature · 5 lines
Regards, Li Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linux.it/pipermail/ltp/attachments/20200923/3fca90f7/attachment.htm>