From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D5380C433EF for ; Mon, 2 May 2022 06:49:14 +0000 (UTC) Received: from localhost ([::1]:35446 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nlPrt-0006Ah-Cc for qemu-devel@archiver.kernel.org; Mon, 02 May 2022 02:49:13 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56716) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nlPoG-0004cQ-Da for qemu-devel@nongnu.org; Mon, 02 May 2022 02:45:30 -0400 Received: from us-smtp-delivery-44.mimecast.com ([205.139.111.44]:25956) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nlPoE-0007rH-En for qemu-devel@nongnu.org; Mon, 02 May 2022 02:45:27 -0400 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-494--zbqUvVJOW-x3FA5McEQGw-1; Mon, 02 May 2022 02:45:13 -0400 X-MC-Unique: -zbqUvVJOW-x3FA5McEQGw-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B9CDD802803; Mon, 2 May 2022 06:45:12 +0000 (UTC) Received: from bahia (unknown [10.39.193.20]) by smtp.corp.redhat.com (Postfix) with ESMTP id 331A79D63; Mon, 2 May 2022 06:45:11 +0000 (UTC) Date: Mon, 2 May 2022 08:45:10 +0200 From: Greg Kurz To: Christian Schoenebeck Subject: Re: [PATCH v5 2/6] 9pfs: fix qemu_mknodat(S_IFSOCK) on macOS Message-ID: <20220502084510.494f2085@bahia> In-Reply-To: <1652707.ZjVTVKMb3i@silver> References: <5815688.WPY9AJzlUa@silver> <20220429163507.2e822089@bahia> <1652707.ZjVTVKMb3i@silver> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 Received-SPF: softfail client-ip=205.139.111.44; envelope-from=groug@kaod.org; helo=us-smtp-delivery-44.mimecast.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org, Keno Fischer , Michael Roitzsch , Will Cohen , Akihiko Odaki Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Fri, 29 Apr 2022 17:20:26 +0200 Christian Schoenebeck wrote: > On Freitag, 29. April 2022 16:35:07 CEST Greg Kurz wrote: > > On Fri, 29 Apr 2022 15:50:35 +0200 > > > > Christian Schoenebeck wrote: > > > On Freitag, 29. April 2022 14:56:50 CEST Greg Kurz wrote: > > > > On Fri, 29 Apr 2022 12:25:11 +0200 > > > > > > > > Christian Schoenebeck wrote: > > > > > mknod() on macOS does not support creating sockets, so divert to > > > > > call sequence socket(), bind() and fchmodat() respectively if S_IFSOCK > > > > > was passed with mode argument. > > > > > > > > > > Link: https://lore.kernel.org/qemu-devel/17933734.zYzKuhC07K@silver/ > > > > > Signed-off-by: Christian Schoenebeck > > > > > --- > > > > > > > > > > hw/9pfs/9p-util-darwin.c | 42 > > > > > +++++++++++++++++++++++++++++++++++++++- > > > > > 1 file changed, 41 insertions(+), 1 deletion(-) > > > > > > > > > > diff --git a/hw/9pfs/9p-util-darwin.c b/hw/9pfs/9p-util-darwin.c > > > > > index e24d09763a..619c403ba7 100644 > > > > > --- a/hw/9pfs/9p-util-darwin.c > > > > > +++ b/hw/9pfs/9p-util-darwin.c > > > > > @@ -74,6 +74,42 @@ int fsetxattrat_nofollow(int dirfd, const char > > > > > *filename, const char *name,> > > > > > > > > > > */ > > > > > > > > > > #if defined CONFIG_PTHREAD_FCHDIR_NP > > > > > > > > > > +static int create_socket_file_at_cwd(const char *filename, mode_t > > > > > mode) { > > > > > + int fd, err; > > > > > + struct sockaddr_un addr = { > > > > > + .sun_family = AF_UNIX > > > > > + }; > > > > > + > > > > > + err = snprintf(addr.sun_path, sizeof(addr.sun_path), "./%s", > > > > > filename); + if (err < 0 || err >= sizeof(addr.sun_path)) { > > > > > > > > According to POSIX [1]: > > > > > > > > The snprintf() function shall fail if: > > > > > > > > [EOVERFLOW] > > > > [CX] [Option Start] The value of n is greater than {INT_MAX}. [Option > > > > End] > > > > > > > > [1] > > > > https://pubs.opengroup.org/onlinepubs/9699919799/functions/snprintf.htm > > > > l > > > > > > > > Since we're passing sizeof(addr.sun_path), I'm pretty sure snprintf() > > > > cannot fail. No big deal. > > > > > > The question is whom you would want to trust on this? POSIX? ISO-C? Clang? > > > BSD? Apple? And for how long into future? I mean in general yes, I would > > > not > > To improve overall portability across all possible hosts, I'd stick to > > POSIX semantics but here this is macOS only code so you can assume > > this is Apple's snprintf(). > > > > > expect it to fail with -1 here either, but there are various different API > > > docs on snprintf() out there, and most of them don't even bother to > > > enumarate which encoding errors may happen. And I'm pretty sure if I'd > > > drop the negative err check here, then Akihiko would slap me for > > > unforeseeable additional error cases on snprintf() that may be added in > > > future. > > > > /o\ ;-) > > > > > Apple's documentation on snprintf() BTW just says: > > > "These functions return a negative value if an error occurs." > > > > How valuable this is !!! ;-) > > > > > So Apple does not even restrict the return value to -1 on errrors, you > > > would also need to expect other negative values. > > > > > > So on doubt, I leave this negative result check for now. ;-) > > > > Fair enough. > > Hey, don't shoot the servant! I'm just trying to find compromises that aim to > suit as many people as possible, as always. :) > Oh I wasn't criticizing your work... rather feeling sorry for the poor documentation of snprintf() on the Apple side. Please go on with the great job you're doing on 9p ! :-) Cheers, -- Greg > Best regards, > Christian Schoenebeck > >