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

Message-ID: <874oiwyakh.fsf@devron.myhome.or.jp>
Date:	Wed, 28 Apr 2010 04:11:58 +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 Wed, Apr 28, 2010 at 01:41:18AM +0900, OGAWA Hirofumi wrote:
>> OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> writes:
>> 
>> >> 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).
>> 
>> Um, please check syslog at same time with dmesg. If there is corruption
>> in syslog, but there is not in dmesg. It sounds like userland problem.
>
> I guess klogd cannot handle that much output.  If you'd add some
> rate limiting that might fix the log corruption, too.

I guess it meant the corruption is in only syslog. Ok, it explains this
problem.

Thanks.
-- 
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/