From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id BD9BA23BEF for ; Tue, 4 Feb 2025 00:46:20 +0100 (CET) Received: (qmail 14127 invoked by uid 550); 3 Feb 2025 23:46:14 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com x-ms-reactions: disallow Received: (qmail 14107 invoked from network); 3 Feb 2025 23:46:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1738626366; bh=i8ZLFQ8HtUPZqRfjSxJcSCeR/rWGvtWo1m//BfnF9Js=; h=Content-Type:Date:Message-Id:Subject:From:To:Mime-Version: Content-Transfer-Encoding:From; b=XJpqN8hGrt2kN5g5ImYnKebgMsbhoADat6uY2A7ltB7IALAsspovpvBXy+g5JYabw rhHuSyrqn7lZgMOKInlaYBVo0GSpOE8TN+0WJdPO1HrQOv31eob6CUetoHrG3wbHJK x4b80eZFy/qpldqqNMH0c1bqpVbhtyy0TAQvfW/o6u4mNaAzyzFWPt7t9Bpu3FUFE3 YKm6dFf1jgPC/oU6i9YbHXhu2xIw30K5r7P5EkaBnZ6PT82piFJJ6x1HYNcLDC1kRs dowdZwa3DzYohg7FA58mZKyuXmxue/J+Ie104xus/NeQaADnr4p9MhEq35jWQOvA7P ptqWyqHNfS+WQ== Content-Type: text/plain; charset=UTF-8 Date: Mon, 03 Feb 2025 23:46:06 +0000 Message-Id: From: "Sertonix" To: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: [musl] hasmntopt(3) match options instead of substring? Hi, people reported issues with mount options not working correctly with ZFS[1] and someone noticed that it could be related to a behaviour difference of hasmntopt(3) between musl and glibc. The manpage[2] mentions that it returns a "substring that matches opt". Just like musl has implemented it this is just strstr. The problem is that it will return "atime" as a option found in "noatime" even though that is probably not what people want. glibc only accepts matches that match the complete option name.[3] Would it be possible for musl to only match options as well? Ideally the wording of hasmntopt(3) would be improved too. [1]: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12382 [2]: https://man.archlinux.org/man/hasmntopt.3.en [3]: https://codebrowser.dev/glibc/glibc/misc/mntent_r.c.html#__hasmntopt