From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1557] dts: File permission issues for files copied to /tmp
Date: Tue, 01 Oct 2024 20:42:37 +0000 [thread overview]
Message-ID: <bug-1557-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1557
Bug ID: 1557
Summary: dts: File permission issues for files copied to /tmp
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
At the Community Lab, some developers have noticed an "annoyance" like this:
User 1 with name User1 runs DTS, and it copies a DPDK tarball over to
/tmp/dpdk.tar.xz on the SUT system. It is extracted and owned by user 1. The
testrun completes without issue.
Later, User 2 tries to run DTS with a DPDK tarball of the same name. In doing
so, the framework tries to delete the previously existing /tmp/dpdk.tar.xz, and
fails as it is running from user User2.
This behavior was also noted today in copying dpdk-devbind.py to the tester
(/tmp/dpdk-devbind.py cannot be removed by all users).
So, then the user has to SSH onto the SUT system, and delete the artifact with
sudo.
Some simple solutions are like:
1. chmod the copied artifacts to allow for all users to delete them.
2. Delete the artifacts as a test run cleanup step.
3. copy all artifacts to something like /tmp/($my_user)/ instead of /tmp/
Or maybe there are some other ideas which are better... feedback is welcome.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3584 bytes --]
reply other threads:[~2024-10-01 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1557-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).