From: Tarkan Erimer <tarkan.erimer@turknet.net.tr>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext4 problem on Linux-2.6.29-rc7-git4
Date: Thu, 12 Mar 2009 17:16:20 +0200 [thread overview]
Message-ID: <49B92744.5040106@turknet.net.tr> (raw)
In-Reply-To: <20090312150235.GD11748@mit.edu>
Theodore Tso wrote:
> It's a warning, not an error; but I didn't expect it to be quite so
> voluminous in terms of log messages. We have a proper fix for it
> queued up for 2.6.30, but it was considered too invasive. So the fix
> was to print a warning which we ratelimited, but it looks like it's
> even with the printk_ratelimit the warnings are too annoying to let
> live. I'll probably fix it to only printk the message once.
>
> - Ted
>
Good to hear that it was just a warning and not a bug/problem ;-)
I think, I can live with these warnings in my dmesg till 2.6.30! :-P
prev parent reply other threads:[~2009-03-12 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 15:32 ext4 problem on Linux-2.6.29-rc7-git4 Tarkan Erimer
2009-03-12 15:02 ` Theodore Tso
2009-03-12 15:16 ` Tarkan Erimer [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=49B92744.5040106@turknet.net.tr \
--to=tarkan.erimer@turknet.net.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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