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: Tue, 1 Dec 2015 10:32:02 -0500	[thread overview]
Message-ID: <20151201153202.GA3179@thunk.org> (raw)
In-Reply-To: <565DAD0A.6030305@oracle.com>

On Tue, Dec 01, 2015 at 03:22:02PM +0100, Vegard Nossum wrote:
> 
> I'm a bit unsure about whether this is really a bug or not; it looks
> like the filesystem is set to panic on error but I still find it weird
> that this behaviour is allowed by default (would it still panic if
> somebody inserted this filesystem on a USB stick and it got automounted?).

If the distribution cares about this, it should automount with mount
option "errors=remount-ro".

> I call mount() with mountflags=0 and data=NULL followed by opendir() and
> readdir(), but if I just a manual mount + ls from the shell I don't see
> the panic at all, just some of the errors, so I thought maybe there's
> some sort of race somewhere?

I'm not able to reproduce this; I'm getting EACCES to the opendir().

But looking at your kernel messages, it's not a bug.

Cheers,

						- Ted

  reply	other threads:[~2015-12-01 15:32 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 [this message]
2015-12-01 16:59   ` Vegard Nossum
2015-12-02 13:41     ` Theodore Ts'o
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=20151201153202.GA3179@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).