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
| ||
|
Date: Tue, 9 May 2017 12:12:44 -0400 From: Jeff Layton <jlayton@...hat.com> To: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org, linux-cifs@...r.kernel.org, linux-nfs@...r.kernel.org, linux-mm@...ck.org, jfs-discussion@...ts.sourceforge.net, linux-xfs@...r.kernel.org, cluster-devel@...hat.com, linux-f2fs-devel@...ts.sourceforge.net, v9fs-developer@...ts.sourceforge.net, linux-nilfs@...r.kernel.org, linux-block@...r.kernel.org, fstests@...r.kernel.org Cc: dhowells@...hat.com, akpm@...ux-foundation.org, hch@...radead.org, ross.zwisler@...ux.intel.com, mawilcox@...rosoft.com, jack@...e.com, viro@...iv.linux.org.uk, corbet@....net, neilb@...e.de, clm@...com, tytso@....edu, axboe@...nel.dk, josef@...icpanda.com, hubcap@...ibond.com, rpeterso@...hat.com, bo.li.liu@...cle.com Subject: [xfstests PATCH v2 2/3] ext4: allow ext4 to use $SCRATCH_LOGDEV The writeback error handling test requires that you put the journal on a separate device. This allows us to use dmerror to simulate data writeback failure, without affecting the journal. xfs already has infrastructure for this (a'la $SCRATCH_LOGDEV), so wire up the ext4 code so that it can do the same thing when _scratch_mkfs is called. Signed-off-by: Jeff Layton <jlayton@...hat.com> --- common/rc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/common/rc b/common/rc index 257b1903359d..8b815d9c8c33 100644 --- a/common/rc +++ b/common/rc @@ -675,6 +675,9 @@ _scratch_mkfs_ext4() local tmp=`mktemp` local mkfs_status + [ "$USE_EXTERNAL" = yes -a ! -z "$SCRATCH_LOGDEV" ] && \ + $mkfs_cmd -O journal_dev $SCRATCH_LOGDEV && \ + mkfs_cmd="$mkfs_cmd -J device=$SCRATCH_LOGDEV" _scratch_do_mkfs "$mkfs_cmd" "$mkfs_filter" $* 2>$tmp.mkfserr 1>$tmp.mkfsstd mkfs_status=$? -- 2.9.3
Powered by blists - more mailing lists