linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: v3.10: unmount won't work
Date: Tue, 14 May 2013 22:09:58 +0200	[thread overview]
Message-ID: <51929A16.8050306@gmx.de> (raw)
In-Reply-To: <51928CB5.2050406@gmx.de>

On 05/14/2013 09:12 PM, Toralf Förster wrote:
> At a stable 32 bit stable Gentoo with kernel v3.10-rc1-113-ga2c7a54 I cannot umount an (EXT4) fs
> which was created in a file located in a tmpfs partition and loop mounted  :
> 
> That file system was used to hold victims files shared via NFSv4 to an user mode linux 
> on which trinity was used to fuzz testing a patched UML guest kernel.

FWIW the numbers are really wrong for /mnt/trinity

# df -m /mnt/trinity/
Filesystem     1M-blocks  Used Available Use% Mounted on
/dev/loop0        183851 31165    143325  18% /mnt/trinity

b/c 257 MB were specified for the file in which the EXT4FS was created:

# ls -lh /mnt/ramdisk/disk0
-rw-r--r-- 1 tfoerste users 257M May 14 20:56 /mnt/ramdisk/disk0

here is the corresponding code snippet :
	FS="ext4"
        dd if=/dev/zero of=/mnt/ramdisk/disk0 bs=1M count=257 2>/dev/null || return 2
        yes | /sbin/mkfs.$FS /mnt/ramdisk/disk0 1>/dev/null || return 3
        sudo su -c "mount -o loop /mnt/ramdisk/disk0 /mnt/trinity/; chmod 777 /mnt/trinity" || return 4

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-05-14 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 19:12 v3.10: unmount won't work Toralf Förster
2013-05-14 20:09 ` Toralf Förster [this message]
2013-05-14 21:12 ` Eric Sandeen
2013-05-16 20:23   ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51929A16.8050306@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).