Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Q qemu
  • 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
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Campbell He
  • qemu
  • Repository
  • qemu
  • tests
  • qemu-iotests
  • 056
Find file BlameHistoryPermalink
  • Fam Zheng's avatar
    iotests: Add regresion test case for write notifier assertion failure · 9cc0f19d
    Fam Zheng authored Dec 01, 2015
    
    
    The idea is to let the top level bs have a big request alignment with
    blkdebug, so that the aio_write request issued from monitor will be
    serialised. This tests that QEMU doesn't crash upon the read request
    from the backup job's write notifier, which is a very special case of
    "reentrant" request.
    
    Signed-off-by: default avatarFam Zheng <famz@redhat.com>
    Message-id: 1448962590-2842-4-git-send-email-famz@redhat.com
    Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
    9cc0f19d