linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15230] oops on ext4 remount with -o barrier
Date: Thu, 4 Feb 2010 22:38:51 GMT	[thread overview]
Message-ID: <201002042238.o14Mcpas025417@demeter.kernel.org> (raw)
In-Reply-To: <bug-15230-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=15230


Eric Sandeen <sandeen@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@redhat.com
         AssignedTo|fs_ext4@kernel-bugs.osdl.or |sandeen@redhat.com
                   |g                           |




--- Comment #1 from Eric Sandeen <sandeen@redhat.com>  2010-02-04 22:38:48 ---
Can you try it with the patch at:

http://marc.info/?l=linux-ext4&m=126523161410367&w=2

?

I think that likely will fix it for you.  ext4 had 2 options for which it tried
to accept -optional- arguments, and was doing that in a way such that if the
arg was given w/ no option things went badly due to the option structure being
uninitialized.

Something else may have changed in the option parsing, but I think it may be
simplest / most obvious to just fix up ext4.

-Eric

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

      reply	other threads:[~2010-02-04 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 22:32 [Bug 15230] New: oops on ext4 remount with -o barrier bugzilla-daemon
2010-02-04 22:38 ` bugzilla-daemon [this message]

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=201002042238.o14Mcpas025417@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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).