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 v5 7/8] fat (exportfs): rebuild directory-inode if fat_dget() fails
Date: Sat, 26 Jan 2013 13:22:02 +0900	[thread overview]
Message-ID: <8738xoshed.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd_Lg8twC3XVX8S3Ncm0ghicvXD0Q75-8amuO2Lz40v8Rw@mail.gmail.com> (Namjae Jeon's message of "Tue, 22 Jan 2013 19:31:45 +0900")

Namjae Jeon <linkinjeon@gmail.com> writes:

> 2013/1/20, OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
>> Namjae Jeon <linkinjeon@gmail.com> writes:
>>
>>> We rewrite patch as your suggestion using dummy inode. Would please
>>> you review below patch code ?
>>
>> Looks like good as initial. Clean and shorter.
>>
>> Next is, we have to think about race. I.e. if real inode was made, what
>> happens? Is there no race?
> Hi OGAWA.
>
> Although checking several routines to check hang case you said, I
> didn't find anything.
> And There is no any race on test result also. Am I missing something ?
> Let me know your opinion.

Hm, it's read-only. So, there may not be race for now, I'm sure there is
race on write path though.

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

  reply	other threads:[~2013-01-26  4:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 13:25 Namjae Jeon
2012-12-03  9:57 ` OGAWA Hirofumi
2012-12-04  6:27   ` Namjae Jeon
2012-12-04  9:31     ` OGAWA Hirofumi
2012-12-05  6:01       ` Namjae Jeon
2012-12-05  9:02         ` OGAWA Hirofumi
2012-12-05 11:56           ` Namjae Jeon
2012-12-15 10:52             ` Namjae Jeon
2012-12-19 16:10               ` OGAWA Hirofumi
2012-12-21  5:03                 ` Namjae Jeon
2012-12-21  5:08                   ` Namjae Jeon
2012-12-21  8:19                     ` OGAWA Hirofumi
2012-12-21 10:15                       ` Namjae Jeon
2012-12-21 10:35                         ` OGAWA Hirofumi
2012-12-21 10:36                           ` OGAWA Hirofumi
2013-01-09  6:24                             ` Namjae Jeon
2013-01-20 11:06                               ` OGAWA Hirofumi
2013-01-22 10:31                                 ` Namjae Jeon
2013-01-26  4:22                                   ` OGAWA Hirofumi [this message]
2013-01-28  7:43                                     ` Namjae Jeon
2013-01-28 13:51                                       ` OGAWA Hirofumi
2013-01-29  5:05                                         ` 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=8738xoshed.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