From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [patch] isdn: fix a wrapping bug in isdn_ppp_ioctl() Date: Wed, 10 Oct 2012 08:52:22 -0700 Message-ID: <1349884342.2035.1.camel@joe-AO722> References: <20121010093816.GA3669@elgon.mountain> <1349864358.2386.27.camel@joe-AO722> <1349874007.2386.42.camel@joe-AO722> <1349880119.2386.46.camel@joe-AO722> <1349882347.2386.47.camel@joe-AO722> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Andreas Schwab , Dan Carpenter , Karsten Keil , "David S. Miller" , Masanari Iida , netdev@vger.kernel.org, kernel-janitors@vger.kernel.org To: David Laight Return-path: Received: from perches-mx.perches.com ([206.117.179.246]:40563 "EHLO labridge.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752426Ab2JJPwY (ORCPT ); Wed, 10 Oct 2012 11:52:24 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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?