Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-dm
  • 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-dm
  • Repository
Switch branch/tag
  • linux-dm
  • drivers
  • net
  • tun.c
Find file BlameHistoryPermalink
  • Jason Wang's avatar
    tuntap: attach queue 0 before registering netdevice · eb0fb363
    Jason Wang authored Dec 02, 2012
    
    
    We attach queue 0 after registering netdevice currently. This leads to call
    netif_set_real_num_{tx|rx}_queues() after registering the netdevice. Since we
    allow tun/tap has a maximum of 1024 queues, this may lead a huge number of
    uevents to be injected to userspace since we create 2048 kobjects and then
    remove 2046. Solve this problem by attaching queue 0 and set the real number of
    queues before registering netdevice.
    Reported-by: default avatarJiri Slaby <jslaby@suse.cz>
    Tested-by: default avatarJiri Slaby <jslaby@suse.cz>
    Signed-off-by: default avatarJason Wang <jasowang@redhat.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    eb0fb363