From: Andrew Morton <akpm@zip.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [patch 15/18] move BH_JBD out of buffer_head.h
Date: Sun, 26 May 2002 13:47:30 -0700 [thread overview]
Message-ID: <3CF149E2.39267363@zip.com.au> (raw)
For historical reasons, ext3 has a private BH state bit which has
global scope. This patch moves it inside ext3.
=====================================
--- 2.5.18/include/linux/buffer_head.h~bh_jbd Sat May 25 23:25:51 2002
+++ 2.5.18-akpm/include/linux/buffer_head.h Sat May 25 23:25:51 2002
@@ -23,7 +23,6 @@ enum bh_state_bits {
BH_Async_Read, /* Is under end_buffer_async_read I/O */
BH_Async_Write, /* Is under end_buffer_async_write I/O */
- BH_JBD, /* Has an attached ext3 journal_head */
BH_Boundary, /* Block is followed by a discontiguity */
BH_PrivateStart,/* not a state bit, but the first bit available
* for private allocation by other entities
--- 2.5.18/include/linux/jbd.h~bh_jbd Sat May 25 23:25:51 2002
+++ 2.5.18-akpm/include/linux/jbd.h Sat May 25 23:25:51 2002
@@ -226,12 +226,13 @@ void buffer_assertion_failure(struct buf
#endif /* JBD_ASSERTIONS */
enum jbd_state_bits {
- BH_JWrite
- = BH_PrivateStart, /* 1 if being written to log (@@@ DEBUGGING) */
- BH_Freed, /* 1 if buffer has been freed (truncated) */
- BH_Revoked, /* 1 if buffer has been revoked from the log */
- BH_RevokeValid, /* 1 if buffer revoked flag is valid */
- BH_JBDDirty, /* 1 if buffer is dirty but journaled */
+ BH_JBD /* Has an attached ext3 journal_head */
+ = BH_PrivateStart,
+ BH_JWrite, /* Being written to log (@@@ DEBUGGING) */
+ BH_Freed, /* Has been freed (truncated) */
+ BH_Revoked, /* Has been revoked from the log */
+ BH_RevokeValid, /* Revoked flag is valid */
+ BH_JBDDirty, /* Is dirty but journaled */
};
BUFFER_FNS(JBD, jbd)
-
reply other threads:[~2002-05-26 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CF149E2.39267363@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.