public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark B <mark@lemna.hr>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: dirty buffer_head, but not marked dirty
Date: Sun, 26 Oct 2003 19:37:22 +0100	[thread overview]
Message-ID: <200310261937.22342.mark@lemna.hr> (raw)
In-Reply-To: <Pine.LNX.4.44.0310261204020.3098-100000@raven.themaw.net>

Hi!

One quick question.

Someone takes a buffer_head via sb_bread(),
modifies the data in it (b_data), and then decides that the modifications are 
not ok, so we want the old one back... 
Is there a function to mark the data trashed or should we simply release it 
with brelse()? 
I think brelse() is not good to do (someone else (or we) may get the trashed 
data with the next call from sb_bread() )

Would something like reiserfs_unmap_buffer() do the job correctly(would it 
force to reread the buffer)?

(I know I could easily keep a copy of it or reverse the changes, but the 
changes are through more blocks, so it would be much harder to restore the 
situation by calling some trash() function on them)


-- 
Mark Burazin 
mark@lemna.hr
---<>---<>---<>---<>---<>---<>---<>---<>---<>
Lemna d.o.o.
http://www.lemna.biz - info@lemna.hr
<>---<>---<>---<>---<>---<>---<>---<>---<>---



      parent reply	other threads:[~2003-10-26 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26  4:42 Some questions about memory allocation and BKL Ian Kent
2003-10-26  9:44 ` Jan Hudec
2003-10-26 11:27   ` Ian Kent
2003-10-26 12:43     ` Jan Hudec
2003-10-26 13:21       ` Ian Kent
2003-10-26 14:01         ` Jan Hudec
2003-10-26 15:59           ` Ian Kent
2003-10-26 15:54             ` Jan Hudec
2003-10-26 18:37 ` Mark B [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=200310261937.22342.mark@lemna.hr \
    --to=mark@lemna.hr \
    --cc=linux-fsdevel@vger.kernel.org \
    /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