lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 28 May 2020 11:00:58 +0900 From: Tetsuhiro Kohada <kohada.t2@...il.com> To: Namjae Jeon <linkinjeon@...nel.org> Cc: Namjae Jeon <namjae.jeon@...sung.com>, kohada.tetsuhiro@...mitsubishielectric.co.jp, mori.takahiro@...mitsubishielectric.co.jp, motai.hirotaka@...mitsubishielectric.co.jp, Sungjong Seo <sj1557.seo@...sung.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 4/4] exfat: standardize checksum calculation >> II tried applying patch to dev-tree (4c4dbb6ad8e8). >> -The .patch file I sent >> -mbox file downloaded from archive >> But I can't reproduce the error. (Both succeed) >> How do you reproduce the error? > I tried to appy your patches in the following order. > 1. [PATCH] exfat: optimize dir-cache > 2. [PATCH 1/4] exfat: redefine PBR as boot_sector > 3. [PATCH 2/4] exfat: separate the boot sector analysis > 4. [PATCH 3/4] exfat: add boot region verification > 5. [PATCH 4/4] exfat: standardize checksum calculation I was able to reproduce it. The dir-cache patch was created based on the HEAD of dev-tree. The 4 patches for boot_sector were also created based on the HEAD of dev-tree. (at physically separated place) I'm sorry I didn't check any conflicts with these patches. I'll repost the patch, based on the dir-cache patched dev-tree. If dir-cache patch will merge into dev-tree, should I wait until then? BR
Powered by blists - more mailing lists