On 2025/3/27 17:28, Yang Ming wrote:
On 2025/3/17 21:56, Stephen Hemminger wrote:
Caution: This is an external email. Please be very careful when
clicking links or opening attachments. See http://nok.it/nsb for
additional information.
On Fri, 14 Mar 2025 18:36:38 +0800
Yang Ming <ming.1.y...@nokia-sbell.com> wrote:
The secordary process should not close socket file for MP
channel before performing MP request synchronization.
This prevents error logs when the secondary process exits
without any operation on the crypto device while the primary
process starts the device.
Case situation:
eal_bus_cleanup has been added in rte_eal_cleanup. But for the
secondary process, rte_eal_cleanup firstly performs
rte_mp_channel_cleanup, which closes socket file for the MP
channel, making mp_fd invalid. Subsequently, eal_bus_cleanup
triggers vdev_cleanup, which calls mp_request_sync to send a
message via the MP channel. Since mp_fd is invalid, error logs
occur.
Error logs occur as below when the secordary process exit:
EAL: failed to send to (/tmp/dpdk/l2hicu/mp_socket) due to Bad
file descriptor
EAL: Fail to send request /tmp/dpdk/l2hicu/mp_socket:
ipsec_mb_mp_msg
USER1: Create MR request to primary process failed.
Function call trace:
1. rte_eal_cleanup->rte_mp_channel_cleanup->close_socket_fd
2. rte_eal_cleanup->eal_bus_cleanup->vdev_cleanup->
rte_vdev_driver->ipsec_mb_remove->ipsec_mb_qp_release->
ipsec_mb_secondary_qp_op->rte_mp_request_sync->mp_request_sync->
send_msg->sendmsg(mp_fd, &msgh, 0);
Fixes: 1cab1a40ea9b ("bus: cleanup devices on shutdown")
Cc: kevin.la...@intel.com
Cc: sta...@dpdk.org
Signed-off-by: Yang Ming <ming.1.y...@nokia-sbell.com>
Looks good, could there be a test?
Acked-by: Stephen Hemminger <step...@networkplumber.org>
Hi Thanks Stephen,
We have some findings for this change in our product test line. I will
do more investigation for this patch.
Brs,
Yang Ming
Hi,
This patch has been tested and functions correctly under normal
conditions. However, during testing, we observed some new error logs in
specific cases. Upon investigation, we identified that these logs
originate from a separate issue, which will be addressed in the next
version of this patch. Additionally, a similar issue may affect FreeBSD,
and I plan to include a fix for that as well in the upcoming patch
series. Please note that the entire patch series has been thoroughly tested.
Brs,
Yang Ming
