From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, hch@lst.de, sandeen@redhat.com,
david@fromorbit.com
Subject: Re: [PATCH 3/3] ecryptfs: drop direct calls to ->bmap
Date: Fri, 14 Sep 2018 15:26:16 +0200 [thread overview]
Message-ID: <20180914132616.GC27382@lst.de> (raw)
In-Reply-To: <20180912122536.31977-4-cmaiolino@redhat.com>
On Wed, Sep 12, 2018 at 02:25:36PM +0200, Carlos Maiolino wrote:
> static sector_t ecryptfs_bmap(struct address_space *mapping, sector_t block)
> {
> + sector_t blk_map = 0;
> + int ret;
> struct inode *inode;
> struct inode *lower_inode;
>
> inode = (struct inode *)mapping->host;
> lower_inode = ecryptfs_inode_to_lower(inode);
> +
> + ret = bmap(lower_inode, &blk_map);
> +
> + return !ret ? blk_map : 0;
This could be simplified to:
static sector_t ecryptfs_bmap(struct address_space *mapping, sector_t block)
{
struct inode *lower_inode = ecryptfs_inode_to_lower(mapping->host);
int ret = bmap(lower_inode, &block);
if (ret)
return 0;
return block;
}
But the idea that we even support ->bmap on ecryptfs sounds way too
dangerous.
next prev parent reply other threads:[~2018-09-14 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 12:25 [PATCH 0/3] Replace direct ->bmap calls by bmap() with error support Carlos Maiolino
2018-09-12 12:25 ` [PATCH 1/3] fs: Enable bmap() function to properly return errors Carlos Maiolino
2018-09-14 13:23 ` Christoph Hellwig
2018-09-14 18:48 ` Carlos Maiolino
2018-09-17 20:55 ` Darrick J. Wong
2018-09-18 6:00 ` Carlos Maiolino
2018-09-12 12:25 ` [PATCH 2/3] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2018-09-14 13:23 ` Christoph Hellwig
2018-09-14 18:56 ` Carlos Maiolino
2018-09-12 12:25 ` [PATCH 3/3] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2018-09-14 13:26 ` Christoph Hellwig [this message]
2018-09-14 18:47 ` Carlos Maiolino
2018-09-17 11:04 ` [PATCH 3/3 V2] " Carlos Maiolino
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=20180914132616.GC27382@lst.de \
--to=hch@lst.de \
--cc=cmaiolino@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.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).