From: Amerigo Wang <amwang@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
Yan Zheng <zheng.yan@oracle.com>, Josef Bacik <jbacik@redhat.com>,
Chris Mason <chris.mason@oracle.com>,
akpm@linux-foundation.org, linux-btrfs@vger.kernel.org,
Sven Wegener <sven.wegener@stealer.net>
Subject: Re: [Patch] btrfs: use file_remove_suid() after i_mutex is held
Date: Mon, 06 Jul 2009 14:24:32 +0800 [thread overview]
Message-ID: <4A5198A0.6030904@redhat.com> (raw)
In-Reply-To: <20090705224823.5679075f@infradead.org>
Arjan van de Ven wrote:
> On Mon, 6 Jul 2009 01:29:14 -0400
> Amerigo Wang <amwang@redhat.com> wrote:
>
>
>> file_remove_suid() should be called with i_mutex held,
>> file_update_time() too. So move them after mutex_lock().
>>
>> Plus, check the return value of kmalloc().
>>
>> Signed-off-by: WANG Cong <amwang@redhat.com>
>>
>> ---
>> diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
>> index 7c3cd24..cd36301 100644
>> --- a/fs/btrfs/file.c
>> +++ b/fs/btrfs/file.c
>> @@ -944,14 +944,17 @@ static ssize_t btrfs_file_write(struct file
>> *file, const char __user *buf, if (count == 0)
>> goto out_nolock;
>>
>> + mutex_lock(&inode->i_mutex);
>> +
>> err = file_remove_suid(file);
>> if (err)
>> - goto out_nolock;
>> + goto out;
>> file_update_time(file);
>>
>> pages = kmalloc(nrptrs * sizeof(struct page *), GFP_KERNEL);
>> + if (!pages)
>> + goto out;
>>
>>
> Hi,
>
> I don't think you can keep this at GFP_KERNEL once you hold i_mutex....
> very likely this needs to now turn into GFP_NOFS!
>
Good point!
Hmm, GFP_KERNEL adds __GFP_FS while GFP_NOFS not...
Just moving that kmalloc() up, before mutex_lock(), I think, can solve
this.
I will update this patch now...
Thanks!
prev parent reply other threads:[~2009-07-06 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 5:29 [Patch] btrfs: use file_remove_suid() after i_mutex is held Amerigo Wang
2009-07-06 5:48 ` Arjan van de Ven
2009-07-06 6:24 ` Amerigo Wang [this message]
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=4A5198A0.6030904@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=chris.mason@oracle.com \
--cc=jbacik@redhat.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sven.wegener@stealer.net \
--cc=zheng.yan@oracle.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