From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com
[210.118.77.11]) by dpdk.org (Postfix) with ESMTP id BF362FE5
for ; Tue, 15 Dec 2015 13:41:25 +0100 (CET)
Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245])
by mailout1.w1.samsung.com
(Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014))
with ESMTP id <0NZE002GUGL0AQA0@mailout1.w1.samsung.com> for dev@dpdk.org;
Tue, 15 Dec 2015 12:41:24 +0000 (GMT)
X-AuditID: cbfec7f5-f79b16d000005389-2d-56700a740a72
Received: from eusync4.samsung.com ( [203.254.199.214])
by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id F5.A6.21385.47A00765; Tue,
15 Dec 2015 12:41:24 +0000 (GMT)
Received: from fedinw7x64 ([106.109.131.169])
by eusync4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0
64bit (built May 5 2014))
with ESMTPA id <0NZE00K2VGKZKK40@eusync4.samsung.com>; Tue,
15 Dec 2015 12:41:24 +0000 (GMT)
From: Pavel Fedin
To: dev@dpdk.org
Date: Tue, 15 Dec 2015 15:41:23 +0300
Message-id: <00c101d13735$e85453d0$b8fcfb70$@samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-index: AdE3Na1tT9Msc3KgSq64UcxjOtb0PA==
Content-language: ru
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsVy+t/xa7olXAVhBlvui1i8+7SdyeJK+092
iyuzpzFaTJ4t5cDi8WvBUlaPvi2rGAOYorhsUlJzMstSi/TtErgyPi/5y1RwjK1i/q1m9gbG
JaxdjJwcEgImEjc3XWWCsMUkLtxbz9bFyMUhJLCUUWLZ51usEM53Rom1678yg1SxCahLnP76
gQXEFhEQkPjcuRisg1mgk1Hi3+WX7CAJYQFlicO3N4CtYBFQlZh55w9YM6+ApcSiV5/ZIGxB
iR+T74ENYhbQkli/8zgThC0vsXnNW2aIkxQkdpx9zQixTE+i6cw+ZogaEYlp/+4xT2AUmIVk
1Cwko2YhGTULScsCRpZVjKKppckFxUnpuUZ6xYm5xaV56XrJ+bmbGCFB/HUH49JjVocYBTgY
lXh4FzDnhwmxJpYVV+YeYpTgYFYS4X34DyjEm5JYWZValB9fVJqTWnyIUZqDRUmcd+au9yFC
AumJJanZqakFqUUwWSYOTqkGRgsVv53tCU0/VlX3l/CuDFmk9cffhWGiWUX/TCajndILVk3Y
3Dj1LbflYXMV+2COCY5eTrk7bxlI9N84rcPw2k/DvK2zZT7rHPND3t8vpTbmMETYbe5dYlX7
/5dcgNeBS3+ubODc6eB47sdetwcBMl6nYj6q1H6fuez7pM5tGV337aJMuQIXKLEUZyQaajEX
FScCAEM/1eZeAgAA
Cc: 'Ilya Maximets' ,
'Dyasly Sergey'
Subject: [dpdk-dev] problem vhost-user sockets
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Tue, 15 Dec 2015 12:41:25 -0000
Hello!
I have a question regarding vhostuser. If we cannot bind to a socket, why do we simply fail with error instead of just unlink()ing
the path before binding?
This causes a very annoying problem with ovs. After ovs is stopped (i use supplied system integration), these sockets are not
removed. Looks like ovs just exits without correct cleanup. This effectively causes my vhostuser interfaces to go down until i clean
them up manually. And i have to do it after every ovs restart, every system reboot, etc. It is very annoying.
I understand that the app should really do correct cleanup upon exit. But what if it abnormally crashes because of some reason
(bug, attack, etc)? Shouldn't it be able to automatically recover?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia