linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: EXT4-fs (device loop0): panic forced after error -- bug or not?
Date: Wed, 2 Dec 2015 08:41:15 -0500	[thread overview]
Message-ID: <20151202134115.GA3356@thunk.org> (raw)
In-Reply-To: <565DD1DB.4060803@oracle.com>

On Tue, Dec 01, 2015 at 05:59:07PM +0100, Vegard Nossum wrote:
> Strange that you get EACCESS, without errors=remount-ro I get:
> 
> open("/dev/loop0", O_RDWR)              = 3
> mkdir("/mnt/ext4", 0755)                = -1 EEXIST (File exists)
> open("ext4.0", O_RDWR)                  = 4
> ioctl(3, LOOP_SET_FD, 0x4)              = 0
> close(4)                                = 0
> ioctl(3, LOOP_SET_STATUS64, {offset=0, number=0, flags=0,
> file_name="ext4.0", ...}) = 0
> mount("/dev/loop0", "/mnt/ext4", "ext4", 0, NULL) = 0
> open("/mnt/ext4", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
> getdents(4, <panic>

What is the source code of your test program, and what version of C
library are you using?  On my system, opendir() is getting translated
to:

openat(AT_FDCWD, "/vdc", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 EACCES (Permission denied)

(It would have saved me time if you had sent me the source of your
test program, BTW.)

Cheers,

					- Ted

  reply	other threads:[~2015-12-02 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 14:22 EXT4-fs (device loop0): panic forced after error -- bug or not? Vegard Nossum
2015-12-01 15:32 ` Theodore Ts'o
2015-12-01 16:59   ` Vegard Nossum
2015-12-02 13:41     ` Theodore Ts'o [this message]
2015-12-14  7:16       ` Vegard Nossum

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=20151202134115.GA3356@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    /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).