[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130406132028.GD28744@parisc-linux.org>
Date: Sat, 6 Apr 2013 07:20:29 -0600
From: Matthew Wilcox <matthew@....cx>
To: Marco Stornelli <marco.stornelli@...il.com>
Cc: linux-fsdevel@...r.kernel.org,
Chris Mason <chris.mason@...ionio.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Theodore Ts'o <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jaegeuk Kim <jaegeuk.kim@...sung.com>,
Steven Whitehouse <swhiteho@...hat.com>,
KONISHI Ryusuke <konishi.ryusuke@....ntt.co.jp>,
Mark Fasheh <mfasheh@...e.com>,
Joel Becker <jlbec@...lplan.org>,
Mike Snitzer <snitzer@...hat.com>,
Alasdair G Kergon <agk@...hat.com>,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
cluster-devel@...hat.com, linux-nilfs@...r.kernel.org,
ocfs2-devel@....oracle.com, linux-mm@...ck.org,
Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 3/4] fsfreeze: manage kill signal when
sb_start_pagefault is called
On Sat, Apr 06, 2013 at 12:05:52PM +0200, Marco Stornelli wrote:
> In every place where sb_start_pagefault was called now we must manage
> the error code and return VM_FAULT_RETRY.
Erm ... in patch 1/4:
static inline void sb_start_pagefault(struct super_block *sb)
{
- __sb_start_write(sb, SB_FREEZE_PAGEFAULT, true);
+ __sb_start_write_wait(sb, SB_FREEZE_PAGEFAULT, false);
}
>
> - sb_start_pagefault(inode->i_sb);
> + ret = sb_start_pagefault(inode->i_sb);
> + if (ret)
> + return VM_FAULT_RETRY;
> ret = btrfs_delalloc_reserve_space(inode, PAGE_CACHE_SIZE);
Does the compiler not warn that you're assigning void to 'ret'? Or was
there some other SNAFU sending these patches?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists