Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752793AbWLWKSb (ORCPT ); Sat, 23 Dec 2006 05:18:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752778AbWLWKSb (ORCPT ); Sat, 23 Dec 2006 05:18:31 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:46300 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752724AbWLWKSa (ORCPT ); Sat, 23 Dec 2006 05:18:30 -0500 Subject: Re: Finding hardlinks From: Arjan van de Ven To: Mikulas Patocka Cc: Jan Harkes , Miklos Szeredi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org In-Reply-To: References: <20061221185850.GA16807@delft.aura.cs.cmu.edu> Content-Type: text/plain Organization: Intel International BV Date: Sat, 23 Dec 2006 11:18:26 +0100 Message-Id: <1166869106.3281.587.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-2.fc6) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 21 > > If user (or script) doesn't specify that flag, it doesn't help. I think > the best solution for these filesystems would be either to add new syscall > int is_hardlink(char *filename1, char *filename2) > (but I know adding syscall bloat may be objectionable) it's also the wrong api; the filenames may have been changed under you just as you return from this call, so it really is a "was_hardlink_at_some_point()" as you specify it. If you make it work on fd's.. it has a chance at least. -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - 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/