From: Costin Chirvasuta <costinc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bufreset deletes b->nbl-1 blocks?
Date: Fri, 12 Aug 2016 19:25:51 +0300 [thread overview]
Message-ID: <CAPv5z_0oEHG-i_La44wLufOKuaQmPjdonc_PU2hVD=7TGRHDLw@mail.gmail.com> (raw)
In-Reply-To: <CAPd04b57YZu8JU1NHeoAE+FkU09dShBV6w9BYD8_WwYR7tXYmA@mail.gmail.com>
I believe bufreset can be called at any time and b->cbi (the current
cached block) can point to anything.
Either way, that block is never returned to the Disc's free list so
that file address won't be reused from that point on.
On Fri, Aug 12, 2016 at 7:16 PM, James A. Robinson <jimr@highwire.org> wrote:
> Have you checked whether or not that final block is
> special in some way? For example only mapped to
> memory and not to disk blocks?
>
> Jim
>
prev parent reply other threads:[~2016-08-12 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 12:30 Costin Chirvasuta
2016-08-12 15:20 ` James A. Robinson
2016-08-12 15:29 ` Costin Chirvasuta
2016-08-12 15:48 ` James A. Robinson
2016-08-12 16:10 ` Costin Chirvasuta
2016-08-12 16:16 ` James A. Robinson
2016-08-12 16:25 ` Costin Chirvasuta [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='CAPv5z_0oEHG-i_La44wLufOKuaQmPjdonc_PU2hVD=7TGRHDLw@mail.gmail.com' \
--to=costinc@gmail.com \
--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).