From: Boaz Harrosh <bharrosh@panasas.com>
To: <dedekind1@gmail.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>, <bhalevy@tonian.com>,
<jack@suse.cz>, Andrew Morton <akpm@linux-foundation.org>,
<adilger.kernel@dilger.ca>, <tytso@mit.edu>,
<hirofumi@mail.parknet.co.jp>, <mikulas@artax.karlin.mff.cuni.cz>,
Al Viro <viro@ZenIV.linux.org.uk>, <hch@infradead.org>,
<dushistov@mail.ru>, <osd-dev@open-osd.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
<linux-ext4@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/8] exofs: remove lock/unlock super
Date: Thu, 16 Aug 2012 15:32:00 +0300 [thread overview]
Message-ID: <502CE840.4060802@panasas.com> (raw)
In-Reply-To: <1345119652.3393.220.camel@sauron.fi.intel.com>
On 08/16/2012 03:20 PM, Artem Bityutskiy wrote:
> On Thu, 2012-08-16 at 12:00 +0200, Marco Stornelli wrote:
>> From: Marco Stornelli <marco.stornelli@gmail.com>
>>
>> Remove lock and unlock super operation.
>>
>> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
>
> Acked-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
Are you sure? It used to be that exofs_sync_fs() could be called
concurrently.
What about two "bash -c sync" calls or a sync and an unmount
in parallel. anything protecting that?
If so then sure, but please let me test first.
Boaz
next prev parent reply other threads:[~2012-08-16 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:00 [PATCH 2/8] exofs: remove lock/unlock super Marco Stornelli
2012-08-16 12:20 ` Artem Bityutskiy
2012-08-16 12:32 ` Boaz Harrosh [this message]
2012-08-16 13:10 ` Artem Bityutskiy
2012-08-16 13:15 ` Boaz Harrosh
2012-08-16 13:23 ` Boaz Harrosh
2012-08-16 13:30 ` Artem Bityutskiy
2012-08-16 13:29 ` Boaz Harrosh
2012-08-16 16:09 ` Marco Stornelli
2012-08-16 13:23 ` Boaz Harrosh
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=502CE840.4060802@panasas.com \
--to=bharrosh@panasas.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@tonian.com \
--cc=dedekind1@gmail.com \
--cc=dushistov@mail.ru \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=osd-dev@open-osd.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.