From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net, "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Subject: Re: [RFC] [PATCH] rpcbind netid declared per-transport
Date: Fri, 31 Aug 2007 11:38:28 -0400 [thread overview]
Message-ID: <46D835F4.4030703@oracle.com> (raw)
In-Reply-To: <1188573228.6649.100.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
Trond Myklebust wrote:
> On Fri, 2007-08-31 at 10:30 -0400, Chuck Lever wrote:
>> Trond Myklebust wrote:
>>> On Fri, 2007-08-31 at 10:08 -0400, Chuck Lever wrote:
>>>
>>>>>
>>>>> +/*
>>>>> + * RFC1833/RFC3530 rpcbind (v3+) well-known netid's.
>>>>> + */
>>>>> +#define RPCB_NETID_UDP "\165\144\160" /* "udp" */
>>>>> +#define RPCB_NETID_TCP "\164\143\160" /* "tcp" */
>>>>> +#define RPCB_NETID_UDP6 "\165\144\160\066" /* "udp6" */
>>>>> +#define RPCB_NETID_TCP6 "\164\143\160\066" /* "tcp6" */
>>> BTW: Any reason why we are using escaped octal instead of plain ascii
>>> here?
>> Is there a guarantee that these C strings will be US-ASCII on *every*
>> platform in every locale on which Linux kernels are built? Z-series,
>> for example?
>>
>> If yes, then we can use a normal string.
> You might have somebody convert all the strings in the kernel into
> EBCDIC, just for fun, but that will make the strings unreadable on the
> computer running the resulting kernel ('cos Linux uses ASCII) and would
> likely break all sorts of kernel-userspace interfaces besides breaking
> this little snippet in the rpcbind code.
Well, according to Harbison & Steele, the C source and eventual
execution character set can be different. I'm not as certain as you are
of the guarantee that the Linux kernel environment is US-ASCII on every
platform from compile to execution. I've actually written C system
programs in OpenEdition on MVS/390.
However, if you are comfortable using just a plain old C string (and
maybe keeping documentation of the US-ASCII requirement in a comment),
have Tom replace the octal strings with C character strings in his patch.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-31 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 13:35 [RFC] [PATCH] rpcbind netid declared per-transport Talpey, Thomas
2007-08-31 14:08 ` Chuck Lever
2007-08-31 14:26 ` Trond Myklebust
2007-08-31 14:30 ` Chuck Lever
2007-08-31 15:13 ` Trond Myklebust
2007-08-31 15:38 ` Chuck Lever [this message]
2007-08-31 16:08 ` Talpey, Thomas
2007-08-31 16:27 ` Chuck Lever
2007-08-31 16:41 ` Talpey, Thomas
2007-08-31 16:59 ` Chuck Lever
2007-08-31 14:33 ` Chuck Lever
2007-08-31 14:32 ` Chuck Lever
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=46D835F4.4030703@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Thomas.Talpey@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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