From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5358745A84; Tue, 1 Oct 2024 22:42:40 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D8C9240268; Tue, 1 Oct 2024 22:42:39 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id ABC8540267 for ; Tue, 1 Oct 2024 22:42:37 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 9A32145A86; Tue, 1 Oct 2024 22:42:37 +0200 (CEST) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: DTS X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: probb@iol.unh.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17278153571.59132F3.1225832 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17278153571.59132F3.1225832 Date: Tue, 1 Oct 2024 22:42:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1557 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.=20 Later, User 2 tries to run DTS with a DPDK tarball of the same name. In doi= ng so, the framework tries to delete the previously existing /tmp/dpdk.tar.xz,= and fails as it is running from user User2.=20 This behavior was also noted today in copying dpdk-devbind.py to the tester (/tmp/dpdk-devbind.py cannot be removed by all users).=20 So, then the user has to SSH onto the SUT system, and delete the artifact w= ith sudo. Some simple solutions are like:=20 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --17278153571.59132F3.1225832 Date: Tue, 1 Oct 2024 22:42:37 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
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 develop=
ers 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.=20

Later, User 2 tries to run DTS with a DPDK tarball of the same name. In doi=
ng
so, the framework tries to delete the previously existing /tmp/dpdk.tar.xz,=
 and
fails as it is running from user User2.=20

This behavior was also noted today in copying dpdk-devbind.py to the tester
(/tmp/dpdk-devbind.py cannot be removed by all users).=20

So, then the user has to SSH onto the SUT system, and delete the artifact w=
ith
sudo.

Some simple solutions are like:=20
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.
=20=20=20=20=20=20=20=20=20=20
= --17278153571.59132F3.1225832--