{"push_id":3845386813,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"545866b5b3115b7de114bdb7883f5ece59b702d4","before":"a58fec168ef5230a4375f81c8eaa1d2912a3ff58","commits":[{"sha":"545866b5b3115b7de114bdb7883f5ece59b702d4","author":{"name":"Steven Luong","email":"a748ea44ad7b179c2313a856d44e1e4eb39869bb@cisco.com"},"message":"devices: vhost handling VHOST_USER_SET_FEATURES\n\nSome combinations of new qemu (2.11) and old dpdk (16.10) may\nsend VHOST_USER_SET_FEATURES at the end of the protocol exchange\nwhich the vhost interface is already declared up and ready.\nUnfortunately, the process of VHOST_USER_SET_FEATURES will cause\nthe interface to go down. Not sure if it is correct or needed.\nBecause there is no additional messages thereafter, the hardware\ninterface stays down.\n\nThe fix is to check the interface again at the end of processing\nVHOST_USER_SET_FEATURES. If it is up and ready, we bring back\nthe hardware interface.\n\nType: fix\n\nChange-Id: I490cd03820deacbd8b44d8f2cb38c26349dbe3b2\nSigned-off-by: Steven Luong <sluong@cisco.com>","distinct":true,"url":"https://api.github.com/repos/FDio/vpp/commits/545866b5b3115b7de114bdb7883f5ece59b702d4"}]}
{"actor":{"display_login":"fdio-github"}}