[dpdk-dev] [RFC 1/2] nfp: unlink the appropriate lock file
Aaron Conole
aconole at redhat.com
Fri Apr 13 00:22:07 CEST 2018
The nfpu_close needs to unlink the lock file associated with the
nfp descriptor, not lock file 0.
Fixes: d12206e00590 ("net/nfp: add NSP user space interface")
Cc: stable at dpdk.org
Signed-off-by: Aaron Conole <aconole at redhat.com>
---
drivers/net/nfp/nfp_nfpu.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/net/nfp/nfp_nfpu.c b/drivers/net/nfp/nfp_nfpu.c
index f11afef35..2ed985ff4 100644
--- a/drivers/net/nfp/nfp_nfpu.c
+++ b/drivers/net/nfp/nfp_nfpu.c
@@ -101,8 +101,12 @@ nfpu_open(struct rte_pci_device *pci_dev, nfpu_desc_t *desc, int nfp)
int
nfpu_close(nfpu_desc_t *desc)
{
+ char lockname[30];
+
rte_free(desc->nspu);
close(desc->lock);
- unlink("/var/lock/nfp0");
+
+ snprintf(lockname, sizeof(lockname), "/var/lock/nfp%d", desc->nfp);
+ unlink(lockname);
return 0;
}
--
2.14.3
More information about the dev
mailing list