mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Cédric Augonnet" <cedric.augonnet@gmail.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Daniel Aragones" <danarag@gmail.com>,
	linux-kernel@vger.kernel.org, Cedric.augonnet@ens-lyon.org
Subject: Re: 2.6.20-mm1 - Oops using Minix 3 file system
Date: Sun, 18 Feb 2007 11:42:54 +0100	[thread overview]
Message-ID: <f56c1ba00702180242l68ea66eds6de8ca7b78436eb9@mail.gmail.com> (raw)
In-Reply-To: <f56c1ba00702171201y1e4ea025t510e4d4e7dbcf3b2@mail.gmail.com>

2007/2/17, Cédric Augonnet <cedric.augonnet@gmail.com>:
> 2007/2/17, Bill Davidsen <davidsen@tmr.com>:
> > Cédric Augonnet wrote:
>
> That is my all point actually, i am not telling i have a valid
> partition. I'm just describing the fact that the minix fs driver is
> making too many assumptions on the partition it is given. For sure
> there must be something nasty about this image, as you told this is
> the duty of the kernel not to mount such a partition if it is not a
> partition. Here I was only giving an example of the way we could trick
> the driver. This is as important as having the driver working
> correctly on valid partitions i suppose.


Eventually the problem got solved  by Andries Bouwer :
http://marc.theaimsgroup.com/?l=linux-mm-commits&m=117176125510900&w=2

Now i can issue a df command on this partition or whatever it may be,
and i obtain a consistent result wiythout any oops.

Regards,
Cédric

      reply	other threads:[~2007-02-18 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 23:00 Cédric Augonnet
2007-02-17 10:55 ` Daniel Aragonés
2007-02-17 13:51   ` Cédric Augonnet
2007-02-17 16:44     ` Daniel Aragonés
2007-02-17 17:53       ` Cédric Augonnet
2007-02-17 18:49         ` Daniel Aragonés
2007-02-17 19:40 ` Bill Davidsen
2007-02-17 20:01   ` Cédric Augonnet
2007-02-18 10:42     ` Cédric Augonnet [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=f56c1ba00702180242l68ea66eds6de8ca7b78436eb9@mail.gmail.com \
    --to=cedric.augonnet@gmail.com \
    --cc=Cedric.augonnet@ens-lyon.org \
    --cc=akpm@linux-foundation.org \
    --cc=danarag@gmail.com \
    --cc=davidsen@tmr.com \
    --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

all inboxes | Powered by JetHome®