Re: [PATCH 1/9] fs: Enable bmap() function to properly return errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 1/9] fs: Enable bmap() function to properly return errors
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 14 Aug 2019 13:14:35 +0200
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, hch@xxxxxx, adilger@xxxxxxxxx, jaegeuk@xxxxxxxxxx, darrick.wong@xxxxxxxxxx, miklos@xxxxxxxxxx, rpeterso@xxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <20190808082744.31405-2-cmaiolino@redhat.com>
References: <20190808082744.31405-1-cmaiolino@redhat.com> <20190808082744.31405-2-cmaiolino@redhat.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Just curious from looking this again - shoudn't the 0 block be turned
into an error by the bmap() function?  At least for the legacy ->bmap
case so that we don't have to carry this cruft around.

Follow-Ups:
- Re: [PATCH 1/9] fs: Enable bmap() function to properly return errors
  - From: Carlos Maiolino

References:
- [PATCH 0/9 V5] New ->fiemap infrastructure and ->bmap removal
  - From: Carlos Maiolino
- [PATCH 1/9] fs: Enable bmap() function to properly return errors
  - From: Carlos Maiolino

Prev by Date: Re: [PATCH 4/9] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap
Next by Date: Re: [PATCH 2/9] cachefiles: drop direct usage of ->bmap method.
Previous by thread: Re: [PATCH 1/9] fs: Enable bmap() function to properly return errors
Next by thread: Re: [PATCH 1/9] fs: Enable bmap() function to properly return errors
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux