| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <559FE440020000F90000E699@relay2.provo.novell.com> Date: Fri, 10 Jul 2015 01:26:56 -0600 From: "Gang He" <ghe@...e.com> To: <akpm@...ux-foundation.org> Cc: <ocfs2-devel@....oracle.com>, "Mark Fasheh" <MFasheh@...e.com>, <rgoldwyn@...e.de>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 0/4] ocfs2: add online file check feature Hi Andrew, Thank for your suggestions. I will sort out a document for ocfs2 online file check feature. Thanks Gang >>> > On Wed, 24 Jun 2015 13:24:17 +0800 Gang He <ghe@...e.com> wrote: > >> When there are errors in the ocfs2 filesystem, >> they are usually accompanied by the inode number which caused the error. >> This inode number would be the input to fixing the file. >> One of these options could be considered: >> A file in the sys filesytem which would accept inode numbers. >> This could be used to communication back what has to be fixed or is fixed. >> You could write: >> $# echo "CHECK <inode>" > /sys/fs/ocfs2/devname/filecheck >> or >> $# echo "FIX <inode>" > /sys/fs/ocfs2/devname/filecheck > > This is a userspace feature so it should have user documentation. > Documentation/filesystems/ocfs2.txt is presumably the appropriate > place. > > And the availability of the complete user documentation will make the > review of this patchset more productive. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists