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 v5 5/8] fat: restructure export_operations
Date: Tue, 04 Dec 2012 18:28:40 +0900 [thread overview]
Message-ID: <87obia17zr.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd_X8Jkq=PdV+dVPTO_EAPHoZ37MynpjvkrPTDahWyUOTA@mail.gmail.com> (Namjae Jeon's message of "Tue, 4 Dec 2012 15:23:27 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
>>> +static struct dentry *fat_fh_to_dentry_nostale(struct super_block *sb,
>>> + struct fid *fh, int fh_len,
>>> + int fh_type)
>>> +{
>>> + struct inode *inode = NULL;
>>> + struct fat_fid *fid = (struct fat_fid *)fh;
>>> + loff_t i_pos;
>>> +
>>> + switch (fh_type) {
>>> + case FILEID_FAT_WITHOUT_PARENT:
>>> + if (fh_len < FAT_FID_SIZE_WITHOUT_PARENT)
>>> + return NULL;
>>> + case FILEID_FAT_WITH_PARENT:
>>> + if ((fh_len < FAT_FID_SIZE_WITH_PARENT) &&
>>> + (fh_type == FILEID_FAT_WITH_PARENT))
>>> + return NULL;
>>
>> Do we have to care (FILEID_FAT_WITH_PARENT and fh_len < 5) here?
>>
>> if (fh_len < 2)
>> return NULL;
>>
>> switch (fh_type) {
>> case FILEID_INO32_GEN:
>> case FILEID_INO32_GEN_PARENT:
>> inode = get_inode(sb, fid->i32.ino, fid->i32.gen);
>> break;
>> }
>>
>> return d_obtain_alias(inode);
>>
>> generic_fh_to_dentry() is above. I wonder why we have to care
>> fat_fid->parent* here.
> Let me think, if ‘subtree’ checking is enabled then we should check
> the length condition over here also? Please share if there are any
> other comments also.
I'm not sure what did you mean. Where is "subtree" check you are
talking? This is fh_to_dentry(), so we don't use parent at all, so
length == 3 is enough?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-12-04 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:24 [PATCH v5 5/8] fat: restructure export_operations Namjae Jeon
2012-12-03 9:51 ` OGAWA Hirofumi
2012-12-04 6:23 ` Namjae Jeon
2012-12-04 9:28 ` OGAWA Hirofumi [this message]
2012-12-05 5:58 ` Namjae Jeon
2012-12-05 8:56 ` OGAWA Hirofumi
2012-12-05 11:45 ` Namjae Jeon
2012-12-05 12:11 ` OGAWA Hirofumi
2012-12-06 7:37 ` Namjae Jeon
2012-12-06 9:24 ` OGAWA Hirofumi
2012-12-06 9:43 ` 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=87obia17zr.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;
as well as URLs for NNTP newsgroup(s).