From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C87C6427E4; Mon, 20 Mar 2023 18:02:59 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5ED33410D0; Mon, 20 Mar 2023 18:02:59 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id C42C640A80 for <dev@dpdk.org>; Mon, 20 Mar 2023 18:02:57 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id A3B4C427E5; Mon, 20 Mar 2023 18:02:57 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1193] examples/vdpa closes port in non signal safe manner Date: Mon, 20 Mar 2023 17:02:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: examples X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stephen@networkplumber.org 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 target_milestone Message-ID: <bug-1193-3@http.bugs.dpdk.org/> Content-Type: multipart/alternative; boundary=16793317770.f0E15Df.1330998 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org --16793317770.f0E15Df.1330998 Date: Mon, 20 Mar 2023 18:02:57 +0100 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=3D1193 Bug ID: 1193 Summary: examples/vdpa closes port in non signal safe manner Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: examples Assignee: dev@dpdk.org Reporter: stephen@networkplumber.org Target Milestone: --- The vdpa sample application does: signal(SIGINT, signal_handler); Then signal_handler() doess vdpa_signal_quit() which calls close_vdpa() close_vdpa() calls rte_vhost_driver_detach_vdpa_device and unregister These close and detach routines are not signal safe. It could cause a race condition in vdpa driver if signal was received and processed by one thread while another thread was in middle of interacting with host. The correct way to handle this is to set a flag in the signal handler, and exit the main processing loop; then cleanup. --=20 You are receiving this mail because: You are the assignee for the bug.= --16793317770.f0E15Df.1330998 Date: Mon, 20 Mar 2023 18:02:57 +0100 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 <html> <head> <base href=3D"https://bugs.dpdk.org/"> </head> <body><table border=3D"1" cellspacing=3D"0" cellpadding=3D"8" class=3D"= bz_new_table"> <tr> <th>Bug ID</th> <td><a class=3D"bz_bug_link=20 bz_status_UNCONFIRMED " title=3D"UNCONFIRMED - examples/vdpa closes port in non signal safe mann= er" href=3D"https://bugs.dpdk.org/show_bug.cgi?id=3D1193">1193</a> </td> </tr> <tr> <th>Summary</th> <td>examples/vdpa closes port in non signal safe manner </td> </tr> <tr> <th>Product</th> <td>DPDK </td> </tr> <tr> <th>Version</th> <td>unspecified </td> </tr> <tr> <th>Hardware</th> <td>All </td> </tr> <tr> <th>OS</th> <td>All </td> </tr> <tr> <th>Status</th> <td>UNCONFIRMED </td> </tr> <tr> <th>Severity</th> <td>normal </td> </tr> <tr> <th>Priority</th> <td>Normal </td> </tr> <tr> <th>Component</th> <td>examples </td> </tr> <tr> <th>Assignee</th> <td>dev@dpdk.org </td> </tr> <tr> <th>Reporter</th> <td>stephen@networkplumber.org </td> </tr> <tr> <th>Target Milestone</th> <td>--- </td> </tr></table> <p> <div class=3D"bz_comment_block"> <pre class=3D"bz_comment_text">The vdpa sample application does: signal(SIGINT, signal_handler); Then signal_handler() doess vdpa_signal_quit() which calls close_vdpa() close_vdpa() calls rte_vhost_driver_detach_vdpa_device and unregister These close and detach routines are not signal safe. It could cause a race condition in vdpa driver if signal was received and processed by one thread while another thread was in middle of interacting with host. The correct way to handle this is to set a flag in the signal handler, and exit the main processing loop; then cleanup. </pre> </div> </p> <hr> <span>You are receiving this mail because:</span> <ul> <li>You are the assignee for the bug.</li> </ul> <div itemscope itemtype=3D"http://schema.org/EmailMessage"> <div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/Vi= ewAction"> =20=20=20=20=20=20=20=20=20=20 <link itemprop=3D"url" href=3D"https://bugs.dpdk.org/show_bug.cgi= ?id=3D1193"> <meta itemprop=3D"name" content=3D"View bug"> </div> <meta itemprop=3D"description" content=3D"Bugzilla bug update notif= ication"> </div> </body> </html>= --16793317770.f0E15Df.1330998--