From: Mogens Kjaer <mk@crc.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS Bug in 2.4.3?
Date: Thu, 26 Apr 2001 12:49:34 +0200 [thread overview]
Message-ID: <3AE7FD3E.ADCC9016@crc.dk> (raw)
In-Reply-To: <986169711.1485.2.camel@neuromancer>
"Thomas J. Baker" wrote:
>
> There is an NFS bug described here
>
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=30944
>
> that seems to have been known about for a while that is not fixed in
> 2.4.3. Is there something wrong with the patch that is discussed?
It works fine for me.
Note, however, the patch should be patched in order to work on the
2.4.2 kernel distributed with rh71.
--- linux-2.4.2-dir.dif Thu Mar 1 14:58:28 2001
+++ linux-2.4.2-dirRH71.dif Thu Apr 26 12:19:34 2001
@@ -111,13 +111,14 @@
diff -u --recursive --new-file linux-2.4.2-fh_align/fs/readdir.c
linux-2.4.2-dir/fs/readdir.c
--- linux-2.4.2-fh_align/fs/readdir.c Mon Dec 11 22:45:42 2000
+++ linux-2.4.2-dir/fs/readdir.c Thu Feb 22 10:47:49 2001
-@@ -315,7 +315,8 @@
+@@ -346,7 +346,9 @@
lastdirent = buf.previous;
if (lastdirent) {
struct linux_dirent64 d;
- d.d_off = file->f_pos;
++ /* d.d_off = file->f_pos; */
+ /* get the sign extension right */
+ d.d_off = (off_t)file->f_pos;
- copy_to_user(&lastdirent->d_off, &d.d_off,
sizeof(d.d_off));
error = count - buf.count;
- }
+ if (copy_to_user(&lastdirent->d_off, &d.d_off,
sizeof(d.d_off)))
+ error = -EFAULT;
(patch to a patch; hm...).
Mogens
--
Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@crc.dk Homepage: http://www.crc.dk
prev parent reply other threads:[~2001-04-26 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 0:01 NFS Bug in 2.4.3? Thomas J. Baker
2001-04-26 10:49 ` Mogens Kjaer [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=3AE7FD3E.ADCC9016@crc.dk \
--to=mk@crc.dk \
--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