I wrote "that's an inode"; now in living colour:
On Mon, Nov 20, 2017 at 08:09:28AM +, Emmanuel Dreyfus wrote:
> 80 81 01 00 00 00 00 00 00 00 00 00 00 00 00 00
di_mode = 0x8180 = 0100600 (mode 600 regular file)
di_nlink = 1
di_oldids = 0 (uninteresting)
di_size = 0
> 0010
On Mon, Nov 20, 2017 at 03:38:32PM -0500, Mouse wrote:
> dholland's identification of the overwrite data as inodes certainly
> does feel provocative, but I'm not sure what to make of it.
Inodes and data blocks should appear in strictly disjoint regions of
the fs image. Therefore, either
On 2017/11/21 17:03, matthew green wrote:
It'll take a little time to write this change. And, it's low level
and important code, so it will take a time to test the stability
before sending pullup request. So,
0) Apply the following change to -current.
> It'll take a little time to write this change. And, it's low level
> and important code, so it will take a time to test the stability
> before sending pullup request. So,
>
> 0) Apply the following change to -current.
>
>
> Index: kern_softint.c
>
