9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Alyssa M via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Hello, RPi fixes and bind -b trouble
Date: Sat, 24 Feb 2024 20:01:39 -0500	[thread overview]
Message-ID: <17088228990.2DDF4.31241@composer.9fans.topicbox.com> (raw)
In-Reply-To: <8acfd2f2-d802-4918-813f-4f903fb5453a@posixcafe.org>

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

Well I had a go at this on my RPi. I altered libc.a to arrange that errstr() removes the error string filename decoration, but print ("%r") doesn't, and wrapped the open() call (as an example) to do its own error string decoration and hand that back to the kernel.

Unfortunately I then looked in the kernel and discovered that namec (which does the decorating) is called in about 50 places. If it stopped decorating error strings, there are potentially a lot of places that would notice, and I haven't chased them all down.  That being so, my enthusiasm for this idea is much dampened, and I think it's dipped below the worth-considering threshold. :(
I'll keep the code I wrote around in case it's ever useful. On the plus side, I learned some things about the libc.a build process. And the awesome mkfile in /sys/src/libc/9syscall.

I think it would still be worth fixing exportfs to strip off any decoration before sending out an error string via Rerror, though, as that would fix v9fs's problem and the nested mounts problem I was looking at earlier.

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tbc78d29ab04652a2-Mb935ad65e7512b2d0a6787a8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1913 bytes --]

  reply	other threads:[~2024-02-25  1:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 15:07 [9fans] " Alyssa M via 9fans
2024-02-04 16:41 ` [9fans] " moody
2024-02-04 16:50   ` Alyssa M via 9fans
2024-02-04 22:19     ` Alyssa M via 9fans
2024-02-22 19:45       ` Alyssa M via 9fans
2024-02-22 20:27         ` Jacob Moody
2024-02-23 12:12           ` Alyssa M via 9fans
2024-02-23 18:18             ` Jacob Moody
2024-02-25  1:01               ` Alyssa M via 9fans [this message]
2024-02-23  8:03         ` Lucio De Re
2024-02-04 16:46 ` moody

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17088228990.2DDF4.31241@composer.9fans.topicbox.com \
    --to=9fans@9fans.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).