From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, hch@lst.de,
darrick.wong@oracle.com, sandeen@sandeen.net
Subject: Re: [PATCH 1/5] fs: Enable bmap() function to properly return errors
Date: Fri, 22 Nov 2019 14:37:01 +0100 [thread overview]
Message-ID: <20191122133701.GA25822@lst.de> (raw)
In-Reply-To: <20191122085320.124560-2-cmaiolino@redhat.com>
On Fri, Nov 22, 2019 at 09:53:16AM +0100, Carlos Maiolino wrote:
> By now, bmap() will either return the physical block number related to
> the requested file offset or 0 in case of error or the requested offset
> maps into a hole.
> This patch makes the needed changes to enable bmap() to proper return
> errors, using the return value as an error return, and now, a pointer
> must be passed to bmap() to be filled with the mapped physical block.
>
> It will change the behavior of bmap() on return:
>
> - negative value in case of error
> - zero on success or map fell into a hole
>
> In case of a hole, the *block will be zero too
>
> Since this is a prep patch, by now, the only error return is -EINVAL if
> ->bmap doesn't exist.
>
> Changelog:
>
> V6:
> - Fix bmap() doc function
> Reported-by: kbuild test robot <lkp@intel.com>
> V5:
> - Rebasing against 5.3 required changes to the f2fs
> check_swap_activate() function
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
The changelog goes under the --- if you really want a per-patch
changelog. I personally find the per-patch changelog horribly
distracting and much prefer just one in the cover letter, though.
Otherwise this looks good, although we really need to kill these
users rather sooner than later..
Signed-off-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2019-11-22 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:53 [PATCH 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2019-11-22 8:53 ` [PATCH 1/5] fs: Enable bmap() function to properly return errors Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig [this message]
2019-11-22 14:02 ` Carlos Maiolino
2019-11-22 14:07 ` Christoph Hellwig
2019-11-22 8:53 ` [PATCH 2/5] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig
2019-11-22 14:04 ` Carlos Maiolino
2019-11-22 8:53 ` [PATCH 3/5] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2019-11-22 8:53 ` [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
2019-11-24 9:56 ` kbuild test robot
2019-11-24 14:52 ` kbuild test robot
2019-11-22 8:53 ` [PATCH 5/5] fibmap: Reject negative block numbers Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-12-10 15:03 [PATCH 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2019-12-10 15:03 ` [PATCH 1/5] fs: Enable bmap() function to properly return errors Carlos Maiolino
2020-01-09 13:30 [PATCH V8 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2020-01-09 13:30 ` [PATCH 1/5] fs: Enable bmap() function to properly return errors 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=20191122133701.GA25822@lst.de \
--to=hch@lst.de \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).