linux-kernel - Suggestion for improving kernel messages on ext3-mount for consistency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <51541493020000A100010188@gwsmtp1.uni-regensburg.de>
Date:	Thu, 28 Mar 2013 09:59:47 +0100
From:	"Ulrich Windl" <Ulrich.Windl@...uni-regensburg.de>
To:	<linux-kernel@...r.kernel.org>
Subject: Suggestion for improving kernel messages on ext3-mount for
 consistency

Hi!

I have a kind of trivial suggestion for improving the kernel messages for ext3-fs mounts to be more consistent and useful:

Most messages for ext3-mounting include the device, like:
kernel: [  823.233892] EXT3-fs (dm-7): using internal journal
kernel: [  823.233899] EXT3-fs (dm-7): mounted filesystem with ordered data mode

However some messages do not include a device, even though they seem device specific. For example:
kernel: [  823.210989] EXT3-fs: barriers not enabled
kernel: [  823.233218] kjournald starting.  Commit interval 15 seconds

This was observed in the current SLES11 SP2 kernel (3.0.58-0.6.6).

I haven't queried the sources, but it looks like an easy change...

BTW: The kjournal threads are also anonymous in the process list (while xfs (for example) names them):
# ps ax |grep journ
  418 ?        S      0:00 [kjournald]
 1070 ?        S      0:00 [kjournald]
 1071 ?        S      0:00 [kjournald]
 1072 ?        S      0:00 [kjournald]
 1073 ?        S      0:00 [kjournald]
 1074 ?        S      0:00 [kjournald]
 1075 ?        S      0:00 [kjournald]
 5461 ?        S      0:00 [kjournald]
 5499 ?        S      0:00 [kjournald]
 5601 ?        S      0:00 [kjournald]
 5642 ?        S      0:00 [kjournald]
 5648 ?        S      0:00 [kjournald]
 5653 ?        S      0:00 [kjournald]
 5661 ?        S      0:00 [kjournald]
 5873 tty1     S+     0:00 grep journ

# ps ax |grep xfs
 5506 ?        S<     0:00 [xfs_mru_cache]
 5507 ?        S<     0:00 [xfslogd]
 5508 ?        S<     0:00 [xfsdatad]
 5509 ?        S<     0:00 [xfsconvertd]
 5510 ?        S      0:00 [xfsbufd/dm-10]
 5511 ?        S      0:00 [xfsaild/dm-10]
 5518 ?        S      0:00 [xfsbufd/dm-11]
 5519 ?        S      0:00 [xfsaild/dm-11]
 5560 ?        S      0:00 [xfsbufd/dm-12]
 5561 ?        S      0:00 [xfsaild/dm-12]
 5593 ?        S      0:00 [xfsbufd/dm-13]
 5594 ?        S      0:00 [xfsaild/dm-13]
 5875 tty1     S+     0:00 grep xfs

Regards,
Ulrich


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/