From: Karsten Keil <kkeil@linux-pingi.de>
To: Joe Perches <joe@perches.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
Andreas Schwab <schwab@linux-m68k.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Karsten Keil <isdn@linux-pingi.de>,
"David S. Miller" <davem@davemloft.net>,
Masanari Iida <standby24x7@gmail.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] isdn: fix a wrapping bug in isdn_ppp_ioctl()
Date: Fri, 12 Oct 2012 09:49:52 +0200 [thread overview]
Message-ID: <5077CBA0.3040707@linux-pingi.de> (raw)
In-Reply-To: <1349884342.2035.1.camel@joe-AO722>
Hi,
Am 10.10.2012 17:52, schrieb Joe Perches:
> On Wed, 2012-10-10 at 16:44 +0100, David Laight wrote:
>>> On Wed, 2012-10-10 at 15:59 +0100, David Laight wrote:
>>>> Seems to me the code is expecting 256 bits of data, not any multiple of int,
>>>> long or anything else.
>>>
>>> include/linux/isdn_ppp.h:#define PPPIOCGCOMPRESSORS _IOR('t',134,unsigned long [8])
>>
>> That doesn't mean the whole thing makes any sense on 64bit systems.
>> A whole load of historic code used 'long' to ensure 32bit.
>> Some of that might have crept into Linux sources.
>
> Very true, but it's exported via copy_to_user.
>
>> Since I suspect there are a maximum of 256 bits on both 32 and 64bit
>> systems, I wouldn't like to guess exactly how any particular 64bit
>> application chooses to check the bitmap.
>>
>> The ioctl constant may be wrong on 64 bit systems.
>
> shrug. Not much to do about it now.
> isdn isn't very active.
>
> Karsten? What do you think?
>
I use ipppd as testbench to test remote connections via different PPP
clients running on a 64 bit system without problems so far - but I did
not use any compressions for some years, so maybe this code was never
tested on 64 bit and at least not on mixed 32/64 bit systems.
If I will find some time, I will check if the compression works.
I did not wrote this part, so I cannot say how the code should work
correctly out of the box, I need to analyze this first by myself.
Karsten
next prev parent reply other threads:[~2012-10-12 7:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 9:42 [patch] isdn: fix a wrapping bug in isdn_ppp_ioctl() Dan Carpenter
2012-10-10 10:19 ` Joe Perches
2012-10-10 10:41 ` Joe Perches
2012-10-10 10:42 ` David Laight
2012-10-10 11:15 ` Joe Perches
2012-10-10 12:05 ` Andreas Schwab
2012-10-10 13:00 ` Joe Perches
2012-10-10 13:58 ` Andreas Schwab
2012-10-10 14:41 ` Joe Perches
2012-10-10 14:59 ` David Laight
2012-10-10 15:19 ` Joe Perches
2012-10-10 15:44 ` David Laight
2012-10-10 15:52 ` Joe Perches
2012-10-12 7:49 ` Karsten Keil [this message]
2012-10-11 2:46 ` David Miller
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=5077CBA0.3040707@linux-pingi.de \
--to=kkeil@linux-pingi.de \
--cc=David.Laight@ACULAB.COM \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=isdn@linux-pingi.de \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=standby24x7@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).