Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-iv
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-iv
  • Repository
Switch branch/tag
  • linux-iv
  • include
  • linux
  • kasan.h
Find file BlameHistoryPermalink
  • Patricia Alfonso's avatar
    KUnit: KASAN Integration · 83c4e7a0
    Patricia Alfonso authored Oct 13, 2020
    Integrate KASAN into KUnit testing framework.
    
            - Fail tests when KASAN reports an error that is not expected
            - Use KUNIT_EXPECT_KASAN_FAIL to expect a KASAN error in KASAN
    	  tests
            - Expected KASAN reports pass tests and are still printed when run
              without kunit_tool (kunit_tool still bypasses the report due to the
              test passing)
    	- KUnit struct in current task used to keep track of the current
    	  test from KASAN code
    
    Make use of "[PATCH v3 kunit-next 1/2] kunit: generalize kunit_resource
    API beyond allocated resources" and "[PATCH v3 kunit-next 2/2] kunit: add
    support for named resources" from Alan Maguire [1]
    
            - A named resource is added to a test when a KASAN report is
              expected
            - This resource contains a struct for kasan_data containing
              booleans representing if a KASAN report is expected and if a
              KASAN report is found
    
    [1] (https://lore.kernel.org/linux-kselftest/1583251361-12748-1-git-send-email-alan.maguire@oracle.com/T/#t
    
    )
    Signed-off-by: default avatarPatricia Alfonso <trishalfonso@google.com>
    Signed-off-by: default avatarDavid Gow <davidgow@google.com>
    Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
    Tested-by: default avatarAndrey Konovalov <andreyknvl@google.com>
    Reviewed-by: default avatarAndrey Konovalov <andreyknvl@google.com>
    Reviewed-by: default avatarDmitry Vyukov <dvyukov@google.com>
    Acked-by: default avatarBrendan Higgins <brendanhiggins@google.com>
    Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Vincent Guittot <vincent.guittot@linaro.org>
    Link: https://lkml.kernel.org/r/20200915035828.570483-3-davidgow@google.com
    Link: https://lkml.kernel.org/r/20200910070331.3358048-3-davidgow@google.com
    
    Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    83c4e7a0