Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932543AbVJMXtq (ORCPT ); Thu, 13 Oct 2005 19:49:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751132AbVJMXtq (ORCPT ); Thu, 13 Oct 2005 19:49:46 -0400 Received: from mx1.redhat.com ([66.187.233.31]:59877 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1751122AbVJMXtq (ORCPT ); Thu, 13 Oct 2005 19:49:46 -0400 Date: Thu, 13 Oct 2005 19:49:34 -0400 From: Alexander Viro To: torvalds@osdl.org Cc: axboe@suse.de, linux-kernel@vger.kernel.org Subject: BLKSECTGET userland API breakage (2.4 and 2.6 incompatible) Message-ID: <20051013234934.GB6711@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1027 Lines: 22 [that had started as "BLKSECTGET 32bit compat is broken"] Situation: all 2.4: BLKSECTGET takes long * and is supported by several block drivers bio-14-pre9: Takes BLKSECTGET to drivers/block/blkpg.c, defining it for all block drivers *AND* making it take unsigned short * 2.5.1-pre2: bio merge all 2.[56] kernels since then: BLKSECTGET takes unsigned short * 32bit compat: unchanged since 2.4 and thus broken on 2.[56] applications: we have seen ones using 2.6 ABI and getting buggered in 32bit compat. Most likely there are some using 2.4 ABI... IMO the least painful variant is to switch 2.6 compat code to match 2.6 native (i.e. use COMPATIBLE_IOCTL()), leave 2.4 as-is and live with the fact of userland ABI change between 2.4 and 2.6... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/