[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWo9eD=0KqVapZ_2vWZfWrrSWauaXMRNvkmdy+4cXgAig@mail.gmail.com>
Date: Thu, 29 May 2014 20:53:29 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: David Howells <dhowells@...hat.com>
Cc: 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,
"J. R. Okajima" <hooanon05@...oo.co.jp>, mszeredi@...e.cz
Subject: Re: Unionmount and overlayfs testsuite
On Thu, May 29, 2014 at 8:44 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Thu, May 29, 2014 at 8:22 PM, David Howells <dhowells@...hat.com> wrote:
>> Sedat Dilek <sedat.dilek@...il.com> wrote:
>>
>>> > TEST_OVERLAYFS=1 ./run.sh
>>> >
>>> > right?
>>> >
>>>
>>> Yes (with my mount-patch applied).
>>>
>>> ( ...and... # umount /lower /upper /mnt )
>>
>> Can you put a couple of echo commands in settings.inc to show which side of
>> the if-statement it goes and also put:
>>
>> echo TEST_OVERLAYFS is $TEST_OVERLAYFS
>>
>> in run.sh and mount_union.sh?
>>
>
> I retried with the new kernel-config...
>
> # modprobe -v overlayfs
> insmod /lib/modules/3.15.0-rc7-58.1-iniza-lockdep/kernel/fs/overlayfs/overlayfs.ko
>
> ...and echo-line changes...
>
> # LC_ALL=C TEST_OVERLAYFS="1" ./run.sh
> [ run.sh ] TEST_OVERLAYFS is 1
> ***
> *** ./run.sh open-plain.test
> ***
> [ mount_union.sh ] TEST_OVERLAYFS is 1
> TEST100: Open O_RDONLY
> - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
> - open_file -r /mnt/a/foo100 -R :xxx:yyy:zzz
> TEST101: Open O_WRONLY
> - open_file -w /mnt/a/foo101 -W q
> /mnt/a/foo101: Test file not on upper filesystem (line 30)
>
> # LC_ALL=C df -h | egrep 'mnt|upper|lower'
> lower_layer 1.9G 240K 1.9G 1% /lower
> upper_layer 1.9G 4.0K 1.9G 1% /upper
> overlayfs 1.9G 4.0K 1.9G 1% /mnt
>
> # find /mnt/ /upper/ /lower/ -name foo101
> /mnt/a/foo101
> /upper/upper/a/foo101
> /lower/a/foo101
>
> # LC_ALL=C ll /mnt/a/foo101 /upper/upper/a/foo101 /lower/a/foo101
> -rw-r--r-- 1 bin bin 12 May 29 20:42 /lower/a/foo101
> -rw-r--r-- 1 bin bin 12 May 29 20:42 /mnt/a/foo101
> -rw-r--r-- 1 bin bin 12 May 29 20:42 /upper/upper/a/foo101
>
> # stat -c foo101 /mnt/ /upper/ /lower/
> foo101
> foo101
> foo101
>
Hmm, why is the generated binary callled "open-file" and in the
scripts I see "open_file"?
I created a symlink in /usr/local/bin/, but that's not fixing it.
- Sedat -
--
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