Re: [PATCH 1/2] Btrfs: include error on messages about failure to write space/inode caches

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

 



On Tue, May 19, 2020 at 2:07 PM David Sterba <dsterba@xxxxxxx> wrote:
>
> On Mon, May 18, 2020 at 05:34:11PM +0100, fdmanana@xxxxxxxxxx wrote:
> > From: Filipe Manana <fdmanana@xxxxxxxx>
> >
> > Currently the error messages logged when we fail to write a free space
> > cache or an inode cache are not very useful as they don't mention what
> > was the error. So include the error number in the messages.
> >
> > Signed-off-by: Filipe Manana <fdmanana@xxxxxxxx>
>
> 1 and 2 added to misc-next, thanks.
>
> As the 2nd patch fixes a problem introduced in this dev cycle it's ok
> push it as a regression fix. But as we're at rc6 I'd prefer to postpone
> it for the merge window time, unless it's really annoying and hinders
> testing.

Agreed. I consider it a very minor thing.

Thanks.



[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux