From: Pascal Schmidt <der.eremit@email.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] ext3 fixes
Date: Mon, 16 Dec 2002 13:57:32 +0100 [thread overview]
Message-ID: <E18NuoO-0000IU-00@neptune.local> (raw)
In-Reply-To: <3DFCE55B.E9C634E2@digeo.com>
On Sun, 15 Dec 2002 21:30:16 +0100, you wrote in linux.kernel:
> Fix it so that we only run ext3_mark_inode_dirty() if the inode was
> successfully instantiated.
After applying your three ext3 fixes to 2.4.20 and rebooting with
data=journal, I get the following message in dmesg which does not
appear with clean 2.4.20 (no matter whether data=ordered or
data=journal):
blk: queue c0370520, I/O limit 4095Mb (mask 0xffffffff)
It appears just after the messages for mounting my ext3 filesystems:
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with journal data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 256k freed
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,71), internal journal
EXT3-fs: mounted filesystem with journal data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,69), internal journal
EXT3-fs: mounted filesystem with journal data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,70), internal journal
EXT3-fs: mounted filesystem with journal data mode.
Is the message just for information or should I worry?
--
Ciao,
Pascal
prev parent reply other threads:[~2002-12-16 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 20:26 [patch] ext3 use-after-free bugfix Andrew Morton
2002-12-16 12:57 ` Pascal Schmidt [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=E18NuoO-0000IU-00@neptune.local \
--to=der.eremit@email.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@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 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.