Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • kernel
  • module.c
Find file BlameHistoryPermalink
  • Kirill A. Shutemov's avatar
    module: do not print allocation-fail warning on bogus user buffer size · cc9e605d
    Kirill A. Shutemov authored Mar 24, 2015
    
    
    init_module(2) passes user-specified buffer length directly to
    vmalloc(). It makes warn_alloc_failed() to print out a lot of info into
    dmesg if user specified insane size, like -1.
    
    Let's silence the warning. It doesn't add much value to -ENOMEM return
    code. Without the patch the syscall is prohibitive noisy for testing
    with trinity.
    
    Signed-off-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Cc: Dave Jones <davej@codemonkey.org.uk>
    Cc: Sasha Levin <sasha.levin@oracle.com>
    Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
    cc9e605d
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7