From: adr <adr@SDF.ORG>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] ramfs bug
Date: Mon, 15 Aug 2022 14:20:57 +0000 (UTC) [thread overview]
Message-ID: <75fdc75b-675d-c8e-b838-107f606f44c@SDF.ORG> (raw)
In-Reply-To: <b4062425dbbe5784ec520d08214bd64f@hamnavoe.com>
On Mon, 15 Aug 2022, Richard Miller wrote:
> A simple fix is to add a reference count to the Ram struct, to
> keep track of how many Fids point to it, and only allow a Ram to
> be re-used if both busy==0 and ref==0. The new 9legacy patch
> ramfs-refcount makes this change.
Thanks for sharing this with the list. It is really hard to keep
track of what and when with 9legacy.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc364b766ff6473bc-Mc0e95938ae16096f4aaad0b7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2022-08-15 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:02 Richard Miller
2022-08-15 14:20 ` adr [this message]
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=75fdc75b-675d-c8e-b838-107f606f44c@SDF.ORG \
--to=adr@sdf.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).