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: Tue, 2 Aug 2022 18:21:56 +1000 From: Daniel Ng <danielng@...gle.com> To: linux-ext4@...r.kernel.org Cc: Sarthak Kukreti <sarthakkukreti@...gle.com> Subject: [BUG] fsck unable to resolve filenames that include '=' Hi, I've run into an issue when trying to use fsck with an ext4 image when it has '=' in its name. Repro steps: 1. fallocate -l 1G test=.img 2. mkfs.ext4 test=.img 3. fsck test=.img Response: 'fsck.ext4: Unable to resolve '<path>/test=.img' Expected: fsck to do it's thing. Observations: Originally I wasn't sure what the source was, I thought that maybe mkfs wasn't creating the image appropriately. However, I've tried: - renaming the image - creating a hard-link to the image Running fsck on either the renamed image, or the hard-link, works as expected. Kernel version: Linux version 4.19.251-13516-ga0bcf8d80077 Environment: Running on a Chromebook Kind regards, Daniel
Powered by blists - more mailing lists