linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Hanse <jaegeuk.hanse@gmail.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 20/21] mm: drop vmtruncate
Date: Fri, 16 Nov 2012 14:39:32 +0800	[thread overview]
Message-ID: <50A5DFA4.2030700@gmail.com> (raw)
In-Reply-To: <5094E4A3.8020409@gmail.com>

On 11/03/2012 05:32 PM, Marco Stornelli wrote:
> Removed vmtruncate

Hi Marco,

Could you explain me why vmtruncate need remove? What's the problem and 
how to substitute it?

Regards,
Jaegeuk

>
> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
> ---
>   include/linux/mm.h |    1 -
>   mm/truncate.c      |   23 -----------------------
>   2 files changed, 0 insertions(+), 24 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index fa06804..95f70bb 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -977,7 +977,6 @@ static inline void unmap_shared_mapping_range(struct address_space *mapping,
>   
>   extern void truncate_pagecache(struct inode *inode, loff_t old, loff_t new);
>   extern void truncate_setsize(struct inode *inode, loff_t newsize);
> -extern int vmtruncate(struct inode *inode, loff_t offset);
>   void truncate_pagecache_range(struct inode *inode, loff_t offset, loff_t end);
>   int truncate_inode_page(struct address_space *mapping, struct page *page);
>   int generic_error_remove_page(struct address_space *mapping, struct page *page);
> diff --git a/mm/truncate.c b/mm/truncate.c
> index d51ce92..c75b736 100644
> --- a/mm/truncate.c
> +++ b/mm/truncate.c
> @@ -577,29 +577,6 @@ void truncate_setsize(struct inode *inode, loff_t newsize)
>   EXPORT_SYMBOL(truncate_setsize);
>   
>   /**
> - * vmtruncate - unmap mappings "freed" by truncate() syscall
> - * @inode: inode of the file used
> - * @newsize: file offset to start truncating
> - *
> - * This function is deprecated and truncate_setsize or truncate_pagecache
> - * should be used instead, together with filesystem specific block truncation.
> - */
> -int vmtruncate(struct inode *inode, loff_t newsize)
> -{
> -	int error;
> -
> -	error = inode_newsize_ok(inode, newsize);
> -	if (error)
> -		return error;
> -
> -	truncate_setsize(inode, newsize);
> -	if (inode->i_op->truncate)
> -		inode->i_op->truncate(inode);
> -	return 0;
> -}
> -EXPORT_SYMBOL(vmtruncate);
> -
> -/**
>    * truncate_pagecache_range - unmap and remove pagecache that is hole-punched
>    * @inode: inode
>    * @lstart: offset of beginning of hole

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-11-16  6:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-03  9:32 [PATCH 20/21] mm: drop vmtruncate Marco Stornelli
2012-11-16  6:39 ` Jaegeuk Hanse [this message]
2012-11-16  7:45   ` Marco Stornelli
  -- strict thread matches above, loose matches on Subject: below --
2012-12-15 11:00 Marco Stornelli
2012-10-20 12:30 Marco Stornelli

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=50A5DFA4.2030700@gmail.com \
    --to=jaegeuk.hanse@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marco.stornelli@gmail.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;
as well as URLs for NNTP newsgroup(s).