1024 is jbd superblock size, and this constant widely used over e2fsprogs code.
from this particular case it’s clear bug as jsb_buffer defined as.
>>
char jsb_buffer[1024];
>>
> 22 нояб. 2018 г., в 2:54, Theodore Y. Ts'o <tytso@xxxxxxx> написал(а):
>
> The summary really isn't right; "panic" is something that kernels do,
> not userspace programs.
>
>> - if (dump_super) {
>> + if (dump_all || dump_super) {
>> e2p_list_journal_super(out_file, jsb_buffer,
>> - current_fs->blocksize, 0);
>> + 1024, 0);
>
> This makes no sense to me. Why is hard-coding the expected blocksize
> to be 1024 a good thing to do here?
>
> - Ted
