Re: [PATCH 02/19] btrfs: handle checksum validation and repair at the storage layer

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

 



On Tue, Jan 17, 2023 at 08:12:22PM +0100, David Sterba wrote:
> The changelog sounds like a good cover letter for a series, overall
> description but lacks more details.

So, I've done a massive split, but I need guidance on what you
want for a changelog.  There is one bit here which I've incorporated:

> - use of mempool must be mentioned in the changelog with explanation
>   that it's the safe usage pattern and why it cannot lead to lockups

but otherwise I'm at at loss.  Do you want descriptions of what the
low-level changes are counter to the normal normal Linux way of
explain why the changes are done an what the high level design
decisions are?  Or is there something else that is not obvious
from the patch and needs more elaboration?  I can't really think
of much that's missing, but maybe it's easy to overlook important
points when you've been staring at the code for half a year.

Here is the current commit text:

http://git.infradead.org/users/hch/misc.git/commitdiff/c88b5ef41a8e0b5daf645eea415ade683e2d8b72



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux