From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deadlock when swapping to FAT
Date: Wed, 18 Mar 2009 01:08:49 +0900 [thread overview]
Message-ID: <87prgg6sj2.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.64.0903170815110.26754@hs20-bc2-1.build.redhat.com> (Mikulas Patocka's message of "Tue, 17 Mar 2009 08:23:28 -0400 (EDT)")
Mikulas Patocka <mpatocka@redhat.com> writes:
> On Sun, 15 Mar 2009, OGAWA Hirofumi wrote:
>
>> Mikulas Patocka <mpatocka@redhat.com> writes:
>>
>> > Note that the same race condition is happening in all the other
>> > filesystems. Maybe move that i_alloc_sem up to ->bmap method caller?
>>
>> It can be. However, I guess locking strategy would be per
>> filesystems. Because the fs may be using i_alloc_sem in get_block
>> already.
>
> Which ones take it in get_block? I grepped for i_alloc_sem and don't see
> them. Besides, it is mostly taken only for read and recursive taking of
> read-lock for read is allowed. It is taken for writes only in truncate.
I don't know which fs take it, and whether i_alloc_sem is enough for
which fs. It was just guess. And important one is locking strategy of
that would be per filesystems. E.g. it seems XFS is taking own lock.
Well, personally, I don't have objection to add i_alloc_sem, however I'm
not sure, what does i_alloc_sem guarantee for other fs.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2009-03-17 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 12:30 Mikulas Patocka
2009-03-12 16:05 ` OGAWA Hirofumi
2009-03-15 1:54 ` Mikulas Patocka
2009-03-15 3:22 ` OGAWA Hirofumi
2009-03-17 12:23 ` Mikulas Patocka
2009-03-17 16:08 ` OGAWA Hirofumi [this message]
2009-03-19 19:34 ` Mikulas Patocka
2009-03-19 22:27 ` OGAWA Hirofumi
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=87prgg6sj2.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.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
all inboxes | Powered by JetHome®