From: Andrew Morton <akpm@zip.com.au>
To: Frank Davis <fdavis@si.rr.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@suse.de>
Subject: Re: 2.5.2-pre8: fs/ext3/super.c compile error
Date: Fri, 04 Jan 2002 22:28:44 -0800 [thread overview]
Message-ID: <3C369D1C.771BA518@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0201050053070.6939-100000@localhost.localdomain>
Frank Davis wrote:
>
> Hello all,
> I haven't seen the following posted.
> While 'make bzImage', I received the following compile error:
> ...
> super.c: In function 'make_rdonly':
> super.c:59: invalid operands to binary !=
> super.c:62: invalid operands to binary +
> make[3]: *** [super.o] Error 1
> make[3]: Leaving directory '/usr/src/linux/fs/ext3'
> ...
This is a piece of debug code - it's enabled by CONFIG_JBD_DEBUG,
and you can just disable that option to make the error go away.
The code in question is designed to tell the disk device driver
to start silently discarding all writes to the underlying device a
certain number of seconds after the filesystem is mounted. This simulates
a machine crash. It is for scripted crash+recovery testing.
The fix is:
--- linux-2.5.2-pre7/fs/ext3/super.c Fri Jan 4 18:48:43 2002
+++ 25/fs/ext3/super.c Fri Jan 4 22:22:03 2002
@@ -56,10 +56,10 @@ int journal_no_write[2];
static void make_rdonly(kdev_t dev, int *no_write)
{
- if (dev) {
+ if (kdev_val(dev)) {
printk(KERN_WARNING "Turning device %s read-only\n",
bdevname(dev));
- *no_write = 0xdead0000 + dev;
+ *no_write = 0xdead0000 + kdev_val(dev);
}
}
prev parent reply other threads:[~2002-01-05 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 5:58 2.5.2-pre8: fs/ext3/super.c compile error Frank Davis
2002-01-05 6:28 ` Andrew Morton [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=3C369D1C.771BA518@zip.com.au \
--to=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=fdavis@si.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox