Messages in this thread | | | Date | Thu, 22 Jun 2023 12:31:37 +0900 | From | Masami Hiramatsu (Google) <> | Subject | Re: [PATCH v3 00/10] tracing: introducing eventfs |
| |
On Wed, 21 Jun 2023 11:42:24 +0000 Ajay Kaher <akaher@vmware.com> wrote:
> > > > On 20-Jun-2023, at 8:32 PM, Steven Rostedt <rostedt@goodmis.org> wrote: > > > > !! External Email > > > > On Mon, 19 Jun 2023 05:38:25 +0000 > > Ajay Kaher <akaher@vmware.com> wrote: > > > >> # of passed: 65 > >> # of failed: 3 > > > > Unrelated to your patches, but have you checked why these fail? Do you have > > the latest tests running on the latest kernel? > > > > Failed test got passed after enabling /proc/kallsyms, using: > echo 0 > /proc/sys/kernel/kptr_restrict
Oh, interesting. It should be 'unresolved' (skipped) if that happens.
[23] event filter function - test event filtering on functions [FAIL] [60] Kprobe events - probe points [FAIL] [106] (instance) event filter function - test event filtering on functions [FAIL]
OK, let me see.
Thanks for reporting!
> Following is the report of ftracetest on Linux v6.4.0-rc7 (with/without eventfs): > # of passed: 68 > # of failed: 0 > # of unresolved: 6 > # of untested: 0 > # of unsupported: 45 > # of xfailed: 0 > # of undefined(test bug): 0 > > If lockdep is enabled getting same warning as reported by 'kernel test robot' for v3 09/10: > https://lore.kernel.org/all/1686640004-47546-1-git-send-email-akaher@vmware.com/ > > >> # of unresolved: 6 > >> # of untested: 0 > >> # of unsupported: 44 > >> # of xfailed: 0 > >> # of undefined(test bug): 0 > >> > >> These results are same with/without eventfs. > > > > I'm hoping to look at these patches this week. > > Yes, please. Thanks. > > -Ajay >
-- Masami Hiramatsu (Google) <mhiramat@kernel.org>
| |