From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
	DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI,
	RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 25044 invoked from network); 30 Mar 2023 14:47:54 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 30 Mar 2023 14:47:54 -0000
Received: (qmail 18188 invoked by uid 550); 30 Mar 2023 14:47:51 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 18150 invoked from network); 30 Mar 2023 14:47:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112; t=1680187659;
        h=to:subject:message-id:date:from:in-reply-to:references:mime-version
         :from:to:cc:subject:date:message-id:reply-to;
        bh=Ryu/hc5YVv0V6YJwSq+ZC9bKAYxhQcSwYzwTZo0EJk0=;
        b=akBe4qx7Uf3HRgOLCDKRXXI+8pvE6CswfxGEKZNXZIWE1gBi0yrt5c0ynAzFUbS1PX
         B1NNvL2qaK78IH9ikGWBsR5URrI3bJnHPB6OOJKmOg6Ni1tbIftRycq94PE91J6oPC6u
         Olznd2xH7bBNK4GR5Y7UrFroVdtlKvU84sjJDW2CyhM8pJgzj9vZb2+wahnOxEyMCgs6
         93lH2J20PeXYMHAMYDjO3ZM/IIwjmVlf5FKSmTYgC0A4f7DTBz9CxnFKalnZn8iufFSf
         lgUyzEQvxTk9rZZRDmRrfncOg38BugXiQUrNVPb2NtwWxVdOgjLPMXWE3Vdu0YnMrZfU
         Cvgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112; t=1680187659;
        h=to:subject:message-id:date:from:in-reply-to:references:mime-version
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=Ryu/hc5YVv0V6YJwSq+ZC9bKAYxhQcSwYzwTZo0EJk0=;
        b=32XBXqlKB/cfT29hY/HiDL3sU8WFmMdN9HmLpGBvG/cXvnnQyr2z4zdiP5fpPFEMRC
         Znlc8spZOf0+EXCKzxeU0KlS/ZPxcQ1lO5ez3FdXD/LuuDB7AeSV8Js7lbc5e29zx2TC
         G4Oec6f49F/Mqa1Zq7SCvRoi+0M4zlt3wRPI3BWsRX637m0VH1dmRn+LZ0QdSSNa9f7l
         3s3CjmZPAH/AOEWangqHQ99+6DGuNI4vaK6KBSW1ppmReA5u03IJmNxnlwuU/6oer/VI
         xby7cxMAQIcHsm2llitcQzWUXTwfJUSFzRaxMTAMRwvLMTFDBs5foKPyemvA6s5stWDb
         2BQQ==
X-Gm-Message-State: AAQBX9fblMjORaZBeVmF+DzzOJKHduVGKI9x5H82m1TjrxtHcJrwwUkV
	NcDO5+KBttF7tUohsJ+cYquzC9K3ybXx8YGfqgUzv6+iJmPJug==
X-Google-Smtp-Source: AKy350YxbXFK01pK8H91vFoJ6Cm/Emzx3ahtqEW2yIb/yaDVr6KM2eJNLx+/7kpLUHPrUwyjYpiU7WmfbXg5piCq6/c=
X-Received: by 2002:a1f:2ed0:0:b0:410:4a2c:1e9a with SMTP id
 u199-20020a1f2ed0000000b004104a2c1e9amr12886767vku.1.1680187658746; Thu, 30
 Mar 2023 07:47:38 -0700 (PDT)
MIME-Version: 1.0
References: <CA+X7ob_Lc3OEmzUChCUAD-AFOtiVLNCQuqaNN1NJCH19LmiP0Q@mail.gmail.com>
 <20230330135703.GC4163@brightrain.aerifal.cx>
In-Reply-To: <20230330135703.GC4163@brightrain.aerifal.cx>
From: =?UTF-8?Q?Matthias_G=C3=B6rgens?= <matthias.goergens@gmail.com>
Date: Thu, 30 Mar 2023 22:47:27 +0800
Message-ID: <CA+X7ob9ss-B9MUjDxp83QZ4+8VrK-GJaDK50UygoWK32TrPrLQ@mail.gmail.com>
To: musl@lists.openwall.com
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [musl] [BUG] hasmntopt weirdness

On Thu, 30 Mar 2023 at 21:57, Rich Felker <dalias@libc.org> wrote:
> I'm pretty sure it was agreed upon at one point that this was a bug,
> but never pursued further.

OK, that's good to know!

> From what I remember, I think hasmntopt needs to check that the match
> found is at the start or immediately follows a comma (unless there is
> some awful way to embed literal commas) and that it's followed by an
> equals sign, comma, or nul terminator. Does this sound correct?

For what it's worth, that's close to what glibc does.

Sorry, I'm new to this: Is there a spec to these things, or do we just copy what
the other C standard libraries are doing?