From: Rusty Russell <rusty@linuxcare.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: NFS: set_bit on an 'int' variable OK for 64-bit?
Date: Fri, 15 Dec 2000 16:47:26 +1100 [thread overview]
Message-ID: <E146niI-00009W-00@halfway> (raw)
In-Reply-To: Your message of "Mon, 11 Dec 2000 17:08:45 BST." <E145WRS-0008A3-00@the-village.bc.nu>
In message <E145WRS-0008A3-00@the-village.bc.nu> you write:
> > since test11, the NFS code uses the set_bit and related routines
> > to manipulate the wb_flags member of the nfs_page struct (nfs_page.h).
> > Unfortunately, wb_flags has still data type 'int'.
>
> NFS is wrong. Rusty did a complete audit of the code and I've been feeding
> some stuff to Linus. That one may have been missed
Yes, didn't grep the headers. Hmm... that's the only one in
include/linux/*.h though.
> > What do you suggest we should do? Fix nfs_page to use a 'long'
> > variable, or change our bitops macros to use ints?
>
> Fix NFS
Yep, it's trivial.
Cheers,
Rusty.
--
Hacking time.
--- working-2.4.0-test12/include/linux/nfs_page.h.~1~ Thu Dec 14 14:20:28 2000
+++ working-2.4.0-test12/include/linux/nfs_page.h Fri Dec 15 16:46:09 2000
@@ -31,10 +31,10 @@
struct page *wb_page; /* page to read in/write out */
wait_queue_head_t wb_wait; /* wait queue */
unsigned long wb_timeout; /* when to read/write/commit */
+ unsigned long wb_flags; /* long req'd for set_bit */
unsigned int wb_offset, /* Offset of read/write */
wb_bytes, /* Length of request */
- wb_count, /* reference count */
- wb_flags;
+ wb_count; /* reference count */
struct nfs_writeverf wb_verf; /* Commit cookie */
};
-
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/
prev parent reply other threads:[~2000-12-17 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 16:51 NFS: set_bit on an 'int' variable OK for 64-bit? Ulrich.Weigand
2000-12-11 17:01 ` Jes Sorensen
2000-12-11 17:08 ` Alan Cox
2000-12-15 5:47 ` Rusty Russell [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=E146niI-00009W-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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.