From: Chris Mason <mason@suse.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: reiserfs-list@namesys.com, jh_lists@fastmail.fm, green@namesys.com
Subject: Re: Oops with in nfsd - 2.4.19-pre6
Date: 13 Nov 2002 13:14:18 -0500 [thread overview]
Message-ID: <1037211258.288.97.camel@tiny> (raw)
In-Reply-To: <20021112182949.45436c95.philippe.gramoulle@mmania.com>
On Tue, 2002-11-12 at 12:29, Philippe
> Do you have a fix that could be used in 2.4.20-(pre|rc) right now ? ( we need quota as well)
>
> This is becoming really critical and even a not 110% tested patch would be welcome.
Ok, I was hoping for some confirmation that you've seen the bug fixed
with the quota code. Which kernel version + list of patches are you
best able to test on? I'll make you patch against that.
-chris
next prev parent reply other threads:[~2002-11-13 18:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:08 Oops with in nfsd - 2.4.19-pre6 JP Howard
2002-10-31 21:30 ` Chris Mason
2002-11-01 14:46 ` Christopher Barry
2002-11-12 17:29 ` Philippe Gramoullé
2002-11-13 18:14 ` Chris Mason [this message]
2002-11-13 18:40 ` Philippe Gramoullé
2002-11-13 20:23 ` Chris Mason
2002-11-14 2:33 ` Chris Mason
2002-11-27 20:54 ` Data-Logging Progess?! (was: Oops with in nfsd - 2.4.19-pre6) Manuel Krause
2002-11-28 10:18 ` Philippe Gramoullé
2002-11-28 19:23 ` Manuel Krause
2002-11-14 16:04 ` Oops with in nfsd - 2.4.19-pre6 Philippe Gramoullé
2002-11-14 16:32 ` Chris Mason
2002-11-14 17:41 ` Philippe Gramoullé
2002-11-14 17:46 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:12 JP Howard
2002-10-29 14:59 Philippe Gramoullé
2002-10-29 15:14 ` Oleg Drokin
2002-10-29 15:20 ` Philippe Gramoullé
2002-10-29 15:26 ` Oleg Drokin
2002-10-31 20:38 ` Chris Mason
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=1037211258.288.97.camel@tiny \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=jh_lists@fastmail.fm \
--cc=philippe.gramoulle@mmania.com \
--cc=reiserfs-list@namesys.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 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.