From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-oi1-x23d.google.com (mail-oi1-x23d.google.com [IPv6:2607:f8b0:4864:20::23d]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id ea39e2c3 for ; Thu, 17 Jan 2019 07:14:08 +0000 (UTC) Received: by mail-oi1-x23d.google.com with SMTP id v184sf2963733oie.6 for ; Wed, 16 Jan 2019 23:14:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:subject:mime-version :x-original-sender:precedence:mailing-list:list-id:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=NozfwfiSsrM/qP9uS1SoEAenWDcdA4MxNiimp+IQnZc=; b=ec6JkSB5N6zr/zhAt86W9miQ6Z3rLYNvmva68ot5wxmpUVtU4zEH3JzoNCpwa4q/rR nNc2ESmM5eu+TFFzHF1Qd4jHXAA8KxEVF3XfiqTAAS8NhUfc7W6jtMkka0G4chA3NxK8 7KzGIZ/uptB1yFqAeXzJ3zSFR678dQH6k+UvuWUQKVW0eTA0jwKo+F2hqsYx29r7Gn1D 2EKEI25NXbiTGyUsyPRAwpoIr9oaUq+udikpiIVd9h358urNay+HmoGJHtguApgZG16u 0ocQic1H1ND5FS0JPN48ISHP9vDdZtIbBBCxqR8+VyhY8ujgeNtp8WXbp25fonLNHuDv Btyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:subject:mime-version:x-original-sender :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=NozfwfiSsrM/qP9uS1SoEAenWDcdA4MxNiimp+IQnZc=; b=fNVLZ83EPdiNpRMISyBwK5lPdASm+TrTBiu/0OhrQ0Z78UKFcAobLoQNSnFFzunjx4 5Ui7KANsxkuj6tY3knGWDPFSrkod4UW4eHpYEjO8bCZzqYLliciWw3Ba/h90aEUJbLOv JUbDvkqyIs1Xn76zf1nAjQUQRrNl2h4spCtkXrloIKyAswgj4WZPcHCGTnjuPIUJCp7i I2FRx6ylbtHafmNLaWt/UOROMm9dn4/wpxvPXHzMBeTJiKkmK8+i+WBxxIuKZL9gqhS3 K7n3pZaeS3V77B8NGcHTAgXQC0vkV4orTwhU/CuFdBhuZR3Msq+81qrlpqGD+Jag1llr qAGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=sender:x-gm-message-state:date:from:to:message-id:subject :mime-version:x-original-sender:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=NozfwfiSsrM/qP9uS1SoEAenWDcdA4MxNiimp+IQnZc=; b=imI1caKHK0kJoMEdnDoLpo6+Rin1pRo4C5EtyuyWdYPkLoTg+A+nE47S4r5DL6Seib utmwYA0SLkdmwCp7lBzz8q8y6G0qikCkspuK929uQj7fwQUrcVSqVBO8ic2Joh+aHyjc CciwLZk3QGsLu7N+Jrce4gBvYUft5K9h1VZETYo0R/k46w3uUj+CDG4XNxxI98ybJGcz pIdnTKHX0co+EfGDmtheR10ltgXz2cwBNVyppNsl8qequXIfdzHevHbz1YsKYnNH/gsY 3l1gsDxfM8ZHM1ExppAClrcnlNmqLCBxblk48rK/dNzXLIr6SPfSuVC+Rx4L+oDNZkYR nUyg== Sender: voidlinux@googlegroups.com X-Gm-Message-State: AJcUukchlgE4JOPTI696w3E9C8tqeLl97heEWSSRh/HZQrFwTHkO4WJS MOrTcqXixBQda/UWhwBrRDc= X-Google-Smtp-Source: ALg8bN60Yj3q0UwE2frSPp40rIw9sclMJ24rUObJbR//gh4VWKkR7P/H8OtXxktylgCmV9uH/XDWAA== X-Received: by 2002:aca:d607:: with SMTP id n7mr116548oig.1.1547709247201; Wed, 16 Jan 2019 23:14:07 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 2002:a9d:27e9:: with SMTP id c96ls5186872otb.10.gmail; Wed, 16 Jan 2019 23:14:06 -0800 (PST) X-Received: by 2002:a9d:da3:: with SMTP id 32mr216041ots.3.1547709246759; Wed, 16 Jan 2019 23:14:06 -0800 (PST) Date: Wed, 16 Jan 2019 23:14:05 -0800 (PST) From: Steven Hum To: voidlinux Message-Id: <76d8f6be-6ddb-4bb6-81f8-3a29482317b0@googlegroups.com> Subject: [void musl] mkfifo buffer exhibiting unexpected behaviour MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_108_1811082789.1547709245959" X-Original-Sender: sdothum@gmail.com Precedence: list Mailing-list: list voidlinux@googlegroups.com; contact voidlinux+owners@googlegroups.com List-ID: X-Google-Group-Id: 289663804196 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , ------=_Part_108_1811082789.1547709245959 Content-Type: multipart/alternative; boundary="----=_Part_109_1904268978.1547709245960" ------=_Part_109_1904268978.1547709245960 Content-Type: text/plain; charset="UTF-8" I posted this on the musl mailing list (after being redirected on the voidlinux reddit forum): > Running this simple test using clock from sutils to produce a repeating one second interval input stream.. > > mkfifo fifo > clock -i 1 -sf "T> stream one" >fifo & > clock -i 1 -sf "D> stream two" >fifo & > cat fifo > > on void musl only the second fifo input stream is displayed. > on void glibc, both input streams are displayed interleaved as expected. > > Are fifo buffers handled differently under musl? The reply was: *No, aside from possible stdio buffering it's entirely a kernel matter.* I looked up the sutils source and see it's flushing after each output, and tried it on an Alpine-based box here (with musl) and could not reproduce what you're seeing. Both outputs are visible and roughly interleaved (although their order sometimes swaps with scheduling, of course). -- So... is this a bug within void musl? Regards, Steven -- You received this message because you are subscribed to the Google Groups "voidlinux" group. To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com. To post to this group, send email to voidlinux@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/76d8f6be-6ddb-4bb6-81f8-3a29482317b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_109_1904268978.1547709245960 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I posted this on the musl mailing list (after being redire= cted on the voidlinux reddit forum):

> Running t= his simple test using clock from sutils to produce a repeating one second i= nterval input stream..
>=C2=A0
> mkfifo fifo
> clock -i 1 -sf "T> stream one" >fifo &
=
> clock -i 1 -sf "D> stream two" >fifo &
<= div>> cat fifo
>=C2=A0
> on void musl only the= second fifo input stream is displayed.
> on void glibc, both = input streams are displayed interleaved as expected.
>=C2=A0
> Are fifo buffers handled differently under musl?
<= div>
The reply was:

No, aside from possible = stdio buffering it's entirely a kernel matter.
I l= ooked up the sutils source and see it's flushing after each output,
and tried it on an Alpine-based box here (with musl) and could not
reproduce what you're seeing. Both outputs are visible and rou= ghly
interleaved (although their order sometimes swaps with sched= uling, of
course).

--
So... is this a bug within void musl?

Regards,
Steven

--
You received this message because you are subscribed to the Google Groups &= quot;voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to voidlinux= +unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid= /voidlinux/76d8f6be-6ddb-4bb6-81f8-3a29482317b0%40googlegroups.com.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_109_1904268978.1547709245960-- ------=_Part_108_1811082789.1547709245959--