linux-kernel - Re: Unionmount and overlayfs testsuite

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUU8BqGUoQdtuqt403NdCBnJnH1-k64bxTM0b_GSfQr1hQ@mail.gmail.com>
Date:	Tue, 3 Jun 2014 11:26:53 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	David Howells <dhowells@...hat.com>
Cc:	"J. R. Okajima" <hooanon05g@...il.com>,
	Miklos Szeredi <miklos@...redi.hu>,
	Al Viro <viro@...iv.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>, apw@...onical.com,
	Felix Fietkau <nbd@...nwrt.org>, neilb@...e.de,
	jordipujolp@...il.com, ezk@....cs.sunysb.edu, mszeredi@...e.cz
Subject: Re: Unionmount and overlayfs testsuite

On Tue, Jun 3, 2014 at 11:18 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> [...]
>>> [ NOTE-2: The call-trace I have seen once (TERMSLASH=0). ]
>>
>> Do you know for which operation?
>>
>
> # echo $TESTS
> open-plain.test open-trunc.test open-creat.test open-creat-trunc.test
> open-creat-excl.test open-creat-excl-trunc.test noent-plain.test
> noent-trunc.test noent-creat.test noent-creat-trunc.test
> noent-creat-excl.test noent-creat-excl-trunc.test sym1-plain.test
> sym1-trunc.test sym1-creat.test sym1-creat-excl.test sym2-plain.test
> sym2-trunc.test sym2-creat.test sym2-creat-excl.test symx-plain.test
> symx-trunc.test symx-creat.test symx-creat-excl.test
> symx-creat-trunc.test truncate.test dir-open.test dir-weird-open.test
> dir-open-dir.test dir-weird-open-dir.test dir-sym1-open.test
> dir-sym1-weird-open.test dir-sym2-open.test dir-sym2-weird-open.test
> readlink.test impermissible.test
>
> # for i in $TESTS ; do echo [ $i ] ; LC_ALL=C TEST_OVERLAYFS=1
> TERMSLASH=1 ./run.sh $i 2>&1 | tee ../run-sh-log_${i}.txt ; dmesg
>>dmesg_${i}.txt ; done
>
> # for i in $TESTS ; do echo [ $i ] ; grep "INFO: possible recursive
> locking detected" dmesg_${i}.txt ; done
> ...
> [ symx-creat-trunc.test ]
> [ truncate.test ]
> [ 1910.007203] [ INFO: possible recursive locking detected ]
> ...
>
> LAST-GOOD: dmesg_symx-creat-trunc.test.txt
>
> FIRST-BAD: dmesg_truncate.test.txt
>
> dmesg files attached.
>

The lockdep appears one time in the logs... I tried several...

     # LC_ALL=C TEST_OVERLAYFS=1 ./run.sh truncate.test

...and see the only lockdep.

Sorry, I cannot say which of the test-no (is that what you mean by
operation?) is causing the lockdep.

Truncate-test results attached.

- Sedat -

View attachment "run-sh-log_truncate-test.txt" of type "text/plain" (4299 bytes)