From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>,
Alan Cox <laughing@shared-source.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac11
Date: 17 Sep 2001 09:47:42 +0200 [thread overview]
Message-ID: <shsvgiicl7l.fsf@charged.uio.no> (raw)
In-Reply-To: <200109170049.f8H0nkEa008317@sleipnir.valparaiso.cl> <m366ail5pp.fsf@giants.mandrakesoft.com>
In-Reply-To: Chmouel Boudjnah's message of "17 Sep 2001 07:57:38 +0200"
>>>>> " " == Chmouel Boudjnah <chmouel@mandrakesoft.com> writes:
> Horst von Brand <vonbrand@sleipnir.valparaiso.cl> writes:
>> Boots and panics immediately "trying to kill init"
> Backout the changes to fs/locks.c or the patch of Trond :
> http://marc.theaimsgroup.com/?l=linux-kernel&m=100019824200351&w=2
Huh? WTF does a patch to the locking code have to do with init?
That particular code is only called if something closes a file on
which POSIX locks are applied. Init doesn't use locking.
The patch *is* required in Alan's tree. Without it, 2 processes that
lock the same file can race and corrupt the i_flock list.
Cheers,
Trond
next prev parent reply other threads:[~2001-09-17 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 19:27 Linux 2.4.9-ac11 Alan Cox
2001-09-17 0:03 ` Linux 2.4.9-ac11 - unresolved Eyal Lebedinsky
2001-09-17 0:49 ` Linux 2.4.9-ac11 Horst von Brand
2001-09-17 5:57 ` Chmouel Boudjnah
2001-09-17 7:44 ` J . A . Magallon
2001-09-17 7:47 ` Trond Myklebust [this message]
2001-09-17 7:56 ` J . A . Magallon
2001-09-17 8:14 ` Matthias Andree
2001-09-17 8:26 ` Trond Myklebust
2001-09-17 8:24 ` Trond Myklebust
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=shsvgiicl7l.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=chmouel@mandrakesoft.com \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.