From: Arjan van de Ven <arjan@infradead.org>
To: Amerigo Wang <amwang@redhat.com>
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>,
Amerigo Wang <amwang@redhat.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: Sun, 5 Jul 2009 22:48:23 -0700 [thread overview]
Message-ID: <20090705224823.5679075f@infradead.org> (raw)
In-Reply-To: <20090706053128.6318.16410.sendpatchset@localhost.localdomain>
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!
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-07-06 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 5:29 Amerigo Wang
2009-07-06 5:48 ` Arjan van de Ven [this message]
2009-07-06 6:24 ` Amerigo Wang
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=20090705224823.5679075f@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--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
Powered by JetHome