mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>,
	Ravishankar N <ravi.n1@samsung.com>,
	Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH 1/5] fat: remove parent_logstart check in fat_get_parent
Date: Mon, 05 Nov 2012 21:27:02 +0900	[thread overview]
Message-ID: <87sj8okzft.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1351389156-2484-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Sun, 28 Oct 2012 10:52:36 +0900")

Namjae Jeon <linkinjeon@gmail.com> writes:

> +		blknr = fat_clus_to_blknr(sbi, parent_logstart);
> +		parent_bh = sb_bread(sb, blknr);
> +		if (!parent_bh) {
> +			fat_msg(sb, KERN_ERR,
> +				"NFS:unable to read cluster of parent directory");
> +			goto out;
>  		}
> +		de = (struct msdos_dir_entry *) parent_bh->b_data;
> +		clus_to_match = fat_get_start(sbi, &de[0]);
> +		search_clus = fat_get_start(sbi, &de[1]);
> +		if (!search_clus)
> +			search_clus = sbi->root_cluster;
> +		brelse(parent_bh);
> +		do {
> +			parent_inode =  fat_traverse_cluster(sb,
> +					search_clus, clus_to_match);
> +			if (IS_ERR(parent_inode) || parent_inode)
> +				break;
> +			search_clus = fat_read_next_clus(sb,
> +							search_clus);
> +			if (search_clus < 0)
> +				break;
> +		} while (search_clus != FAT_ENT_EOF);
>  	}
>  out:
>  	brelse(dotdot_bh);

I started to understand what is doing this with cleanup. It is really
strange and duplicates many codes with bugs.

So, please replace whole FAT nfs patches in -mm to review whole at next
patchset. And sorry, but please think whole more carefully.

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

  parent reply	other threads:[~2012-11-05 12:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28  1:52 Namjae Jeon
2012-10-31  0:37 ` OGAWA Hirofumi
2012-10-31  0:51   ` Namjae Jeon
2012-11-05 12:27 ` OGAWA Hirofumi [this message]
2012-11-06  4:16   ` 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=87sj8okzft.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=a.sahrawat@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=ravi.n1@samsung.com \
    /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

Powered by JetHome