From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C426F385802F; Mon, 18 Dec 2023 18:55:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C426F385802F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1702925720; bh=o1Ked6vwaIk6rDxwPZTtVHOwri7a6lgqgxeG+Qfe3fE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eNZS6ebwDhfblh+0NW7bgIJ3h3dOBsr1126i3P5GbbVHbxMyUciNx+kmquAIqqGGG ZgS233JoQt3OEujmabwkEl7uomHEb6uAWx3ECitTZpVmPdAYROyic9X0eKMzjnW5o/ r1S/4TerQN6o33pJNbUyHkCQHDpioIr0ijghzK1w= From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31117] transport failures Date: Mon, 18 Dec 2023 18:55:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wcohen at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31117 --- Comment #3 from William Cohen --- I did some investigation on this with the map_hash_SSI.stp transport failur= es.=20 Some fixes of the diagnostic print code for the transport layer were made s= o it compiles on fedora 39. The __stp_print_flush code expects there to be enou= gh room to write out the _stp_trace header (12 bytes) in the space returned by _stp_data_write_reserve(). However, there are cases where _stp_data_write_reserve() returned less space (5 and 9 bytes). The causes = the _stp_print_flush to fail and increment _stp_transport_failures. That certa= inly needs to be fixed. I had some additional code in the runtime to print out each time _stp_print_flush had a failure. I didn't see that triggering with the sys.= stp. Looks like will need to additional diagnostic prints to figure out what is going on with the sys.stp output. --=20 You are receiving this mail because: You are the assignee for the bug.=