Re: [LTP] [PATCH v3] madvise11.c:Check loadable module before rmmod

[Cyril Hrubis <chrubis@suse.cz>]

Hi!
> > +int tst_buildin_driver(const char *driver)
> > +{
> > +       return !tst_search_driver(driver, "modules.buildin");
> > +}
> > +
> >  int tst_check_driver(const char *driver)
> >  {
> >  #ifdef __ANDROID__
> > 
> 
> Try use above implementation but i found another TWARN : (
> 
> localhost:/home/ltp/testcases/kernel/syscalls/madvise # ./madvise11
> tst_test.c:1560: TINFO: Timeout per run is 0h 01m 00s
> madvise11.c:396: TINFO: Spawning 5 threads, with a total of 800 memory pages
> madvise11.c:165: TINFO: Thread [3] returned 0, succeeded.
> madvise11.c:165: TINFO: Thread [1] returned 0, succeeded.
> madvise11.c:165: TINFO: Thread [2] returned 0, succeeded.
> madvise11.c:165: TINFO: Thread [4] returned 0, succeeded.
> madvise11.c:165: TINFO: Thread [0] returned 0, succeeded.
> madvise11.c:199: TPASS: soft-offline / mmap race still clean
> madvise11.c:327: TWARN: open(/sys/kernel/debug/hwpoison/unpoison-pfn,1,0000) failed: ENOENT (2) !!!!

That's strange, this should be equivalent to the modinfo patch you send,
at least the modinfo parses the same file.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp