mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: koenig@tat.physik.uni-tuebingen.de, torvalds@transmeta.com
Cc: Andries.Brouwer@cwi.nl, aeb@veritas.com, emoenke@gwdg.de,
	eric@andante.org, kobras@tat.physik.uni-tuebingen.de,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: isofs broken (2.2 and 2.4)
Date: Mon, 18 Dec 2000 13:33:53 +0100 (MET)	[thread overview]
Message-ID: <UTC200012181233.NAA176015.aeb@aak.cwi.nl> (raw)

    From koenig@orion.tat.physik.uni-tuebingen.de Mon Dec 18 11:34:14 2000

    On Nov 17, Linus Torvalds wrote:

    > ...

    better you'd have tested it;)  while Andries' patch works fine (2 CDs of
    data copied and checked a bit, seems to work ok with no obvious problems)
    your new patch still shows a number of problems:

    I've got a SIGSEGV in "find" and ...

Ah yes, but Nov 17 and 2.4.0test10 is ancient history.
You do not mention a kernel version, but if it is older
than 2.4.0test12, upgrade.

(Before 2.4.0test11: a few complaints. On 2.4.0test11: a deluge
of complaints. On later kernels: one or two complaints. Must still
look at the case where someone has problems with isofs over nfs -
maybe this is nfs-related, not isofs-related.)

(The story here was interesting: Linus' patch did part of the
work required, good enough for most people. Nevertheless there were
many complaints, and it turned out that gcc 2.95.2 mistranslated
the code. Removing a superfluous line made things work again,
leaving us worried how many other problems in kernel and user
software are caused by this compiler bug. Then I added the part of
my patch that Linus hadnt done yet, so now all should be well again.)

Andries

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-18 13:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18 12:33 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-18  0:17 Andries.Brouwer
2000-11-18  1:21 ` Linus Torvalds
2000-11-18  4:33   ` Keith Owens
2000-11-18  4:50     ` Linus Torvalds
2000-11-17 23:33 Andries.Brouwer
2000-11-17 23:51 ` Linus Torvalds
     [not found] <UTC200011172141.WAA134635.aeb@aak.cwi.nl>
2000-11-17 22:26 ` Harald Koenig
2000-11-17 21:12 Andries.Brouwer
2000-11-17 21:20 ` Harald Koenig
2000-11-17 22:29   ` Linus Torvalds
2000-11-17 22:55     ` Harald Koenig
2000-11-17 23:46       ` Linus Torvalds
2000-11-21 20:03         ` Harald Koenig
2000-11-17 23:53       ` Linus Torvalds
2000-11-17  0:26 Andries.Brouwer
2000-11-17 20:29 ` Harald Koenig
2000-11-16  1:53 Andries.Brouwer
2000-11-16  2:31 ` Linus Torvalds
2000-11-15 19:23 Harald Koenig
2000-11-16  0:11 ` Andries Brouwer
2000-11-16  0:52   ` Linus Torvalds
2000-11-16  1:16   ` Linus Torvalds
2000-11-16  1:33     ` Linus Torvalds

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=UTC200012181233.NAA176015.aeb@aak.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=aeb@veritas.com \
    --cc=emoenke@gwdg.de \
    --cc=eric@andante.org \
    --cc=kobras@tat.physik.uni-tuebingen.de \
    --cc=koenig@tat.physik.uni-tuebingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®