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.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10647 invoked from network); 24 Jul 2023 04:27:06 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 24 Jul 2023 04:27:06 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Mon Jul 24 00:20:33 -0400 2023 Received: from abbatoir (pool-108-27-53-161.nycmny.fios.verizon.net [108.27.53.161]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id af481f40 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Sun, 23 Jul 2023 21:20:30 -0700 (PDT) Message-ID: To: 9front@9front.org Date: Mon, 24 Jul 2023 00:20:29 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: module extension core high-performance optimizer Subject: Re: [9front] Re: [PATCH] make exportfs give "standard" error for file does exist Reply-To: 9front@9front.org Precedence: bulk Quoth Anthony Martin : > Jacob Moody once said: > > The problem is that exportfs sends the errstr back from what > > it gets from open(2). The kernel gives you back the path attempted > > to be accessed in quotes prefixed to 'does not exist'. > > Every fileserver using Enotexist would not fix exportfs causing > > this issue with v9fs. > > I understand. That's partly why I suggested sending a patch > to lkml. They use memcmp on the errstr but they should be > doing the equivalent of strstr (like Go's syscall package). > > Cheers, > Anthony note, the problem with strstr is that walking to a file named 'file does not exist' may confuse the caller; this is why I would like to move to a convention where the "well known" error is at a well known location.