linux-kernel - Re: fat: excessive log spamming due to corrupted fs

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Apr 2010 20:21:56 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Johannes Stezenbach <js@...21.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: fat: excessive log spamming due to corrupted fs

Johannes Stezenbach <js@...21.net> writes:

> On Tue, Apr 27, 2010 at 06:48:04PM +0900, OGAWA Hirofumi wrote:
>> Johannes Stezenbach <js@...21.net> writes:
>> 
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystem error lidAT: Filesysalid cluster chain (i_pos 34568)
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystem ealid cluster chain (i_pos 3AT: Fiesysalid cluster chain (i_pos 34568)
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystem ealid cluster chain (i_pos 3AT: Fesystalid cluster chain (i_pos 34568)
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystem alid cluster chain (i_pos 3AT: Fiesyalid cluster chain (i_pos 34568)
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystem ealid cluster chain (i_pos AT: Fiesystalid cluster chain (i_pos 34568)
>> > Apr 22 16:30:18 zzz kernel: FAT: Filesystealid cluster chain (i_pos 3AT: Fiesystalid cluster chain (i_pos 34568)
>> 
>> I have no idea about message corruption, vfat just call vprintf() for
>> it. I'll see current vprintf() locking stuff.
>
> I think multiple printk per line is prone to corruption on SMP, see the
> comment about KERN_CONT in kernel.h.  But maybe it only happens
> for /var/log/kern.log and my xconsole when generating too much
> output too quickly, "dmesg -s 10000000 | less" did not show
> the corruption (but only shows ~2700 lines out of the ~10000).
> But I think fat should use vprintf() to a buffer and then one printk()
> instead of multiple printk + vprintk.

I think KERN_CONT issue doesn't explain this corruption (i.e. preempted
at middle of vprintk()), so even if this is one vprintk(), this will not
be fixed. One of possibility is buffer overflow of printk, so truncated
the message, but of course, I'm not sure at least for now, and I'm not
checking current printk stuff yet.

Thanks.

> In xconsole it looks like this:
>
> Apr 27 12:06:45 zzz kernel: <systerrouster chain (i_pos 34568)
> Apr 27 12:06:45 zzz kernel: <systeerroruster chain (i_pos 34568)
> Apr 27 12:06:45 zzz kernel: <systeerroruster chain (i_pos 34568)
> Apr 27 12:06:45 zzz kernel: <3systerroruster chain (i_pos 34568)
> Apr 27 12:06:45 zzz kernel: uster chain (i_pos 34568)
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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/