From: moody@posixcafe.org
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: Hello, RPi fixes and bind -b trouble
Date: Sun, 4 Feb 2024 11:41:51 -0500 [thread overview]
Message-ID: <17070649110.Bb83425E.69346@composer.9fans.topicbox.com> (raw)
In-Reply-To: <17070592670.E7CF6327b.7700@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
The issue with exportfs and linux v9fs has been fixed in 9front commit 6eed7a47863553bab31c7f9b1b5b314989efc640. It is regrettable that we had to shift around the err string to make linux happy, but I have no interest in getting involved with changing it on the linux side.
That issue with bind seems to me to be a bug in your walk code, the way the devmnt stuff works is that it walks down the union list and stops when a server returns that a file exists via walk. Like what you have is a server that is returning "yes I have this file" via walk, but when actually reading the directory, it does not show it. Just my guess anyway.
I plan to look in to that tapefs bug. 9front hasn't touched this code and I agree something seems fishy. Thank you for debugging this, I'll test it out and commit a fix.
Thanks,
moody
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tbc78d29ab04652a2-M50513125385a653fa0ed3084
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1606 bytes --]
next prev parent reply other threads:[~2024-02-04 16:42 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 ` moody [this message]
2024-02-04 16:50 ` [9fans] " 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
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17070649110.Bb83425E.69346@composer.9fans.topicbox.com \
--to=moody@posixcafe.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).