Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • I ipipe-x86
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Analytics
    • Analytics
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomaixenomai
  • ipipe-x86
  • Repository
  • ipipe-x86
  • drivers
  • nvme
  • target
  • rdma.c
Find file Blame History Permalink
  • Sagi Grimberg's avatar
    nvmet: don't return "any" ip address in discovery log page · 4c652685
    Sagi Grimberg authored Jan 24, 2018
    
    
    Its perfectly valid to assign a nvmet port to listen on "any"
    IP address (traddr 0.0.0.0 for ipv4 address family) for IP based
    transport ports. However, we must not return this address in
    discovery log entries. Instead we need to return the address
    where the request was accepted on (req->port address).
    
    Since this is nvme transport specific, introduce an optional
    .disc_traddr interface that is designed to check that a
    port in question is bound to "any" IP address and if so, set
    the traddr from the port where the request came from.
    
    Reviewed-by: default avatarJohannes Thumshirn <jthumshirn@suse.de>
    Signed-off-by: default avatarSagi Grimberg <sagi@grimberg.me>
    Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
    4c652685

Imprint & Privacy Policy