mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
	linux-kernel@vger.kernel.org, joe@perches.com,
	Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: [PATCH 2/2] fat: use fat_msg_ratelimit in fat__get_entry.
Date: Wed, 16 May 2012 00:11:32 +0900	[thread overview]
Message-ID: <8762bxo4wr.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1337093193-3999-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Tue, 15 May 2012 10:46:33 -0400")

Namjae Jeon <linkinjeon@gmail.com> writes:

> When application tried to lookup(opendir/readdir/stat) 5000 files in plugging usb device formatted by FAT, If unplugging usb device while lookup files, so many message occured like the below log. and currently it make app slow.
> So this patch use fat_msg_ratelimit function about this message to decrease this messages.
>
> #> ./file_lookup_testcase ./files_directory/
> [   57.768000] usb 2-1.4: USB disconnect, device number 4

[...]

> [   58.040000] FAT-fs (sda1): Directory bread(block 396818) failed
> [   58.048000] FAT-fs (sda1): Directory bread(block 396819) failed
> [   58.052000] FAT-fs (sda1): Directory bread(block 396820) failed
> [   58.060000] FAT-fs (sda1): Directory bread(block 396821) failed

Thanks.

Please handle those patches, Andrew.

> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
> Signed-off-by: Amit Sahrawat <amit.sahrawat83@gmail.com>
> Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
> ---
>  fs/fat/dir.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fat/dir.c b/fs/fat/dir.c
> index aca191b..6eaa28c 100644
> --- a/fs/fat/dir.c
> +++ b/fs/fat/dir.c
> @@ -98,8 +98,8 @@ next:
>  
>  	*bh = sb_bread(sb, phys);
>  	if (*bh == NULL) {
> -		fat_msg(sb, KERN_ERR, "Directory bread(block %llu) failed",
> -		       (llu)phys);
> +		fat_msg_ratelimit(sb, KERN_ERR,
> +			"Directory bread(block %llu) failed", (llu)phys);
>  		/* skip this block */
>  		*pos = (iblock + 1) << sb->s_blocksize_bits;
>  		goto next;

-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2012-05-15 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 14:46 Namjae Jeon
2012-05-15 15:11 ` OGAWA Hirofumi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-13 11:03 Namjae Jeon
2012-05-13 14:24 ` OGAWA Hirofumi
2012-05-13 15:46 ` Joe Perches
2012-05-13 16:07   ` OGAWA Hirofumi
2012-05-13 16:21     ` Joe Perches
2012-05-13 16:39       ` OGAWA Hirofumi
2012-05-13 23:03         ` Namjae Jeon

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=8762bxo4wr.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=amit.sahrawat83@gmail.com \
    --cc=joe@perches.com \
    --cc=linkinjeon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®