Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752910AbWLWOAV (ORCPT ); Sat, 23 Dec 2006 09:00:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752964AbWLWOAU (ORCPT ); Sat, 23 Dec 2006 09:00:20 -0500 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:47790 "EHLO artax.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752910AbWLWOAT (ORCPT ); Sat, 23 Dec 2006 09:00:19 -0500 Date: Sat, 23 Dec 2006 15:00:18 +0100 (CET) From: Mikulas Patocka To: Arjan van de Ven Cc: Jan Harkes , Miklos Szeredi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: Finding hardlinks In-Reply-To: <1166869106.3281.587.camel@laptopd505.fenrus.org> Message-ID: References: <20061221185850.GA16807@delft.aura.cs.cmu.edu> <1166869106.3281.587.camel@laptopd505.fenrus.org> X-Personality-Disorder: Schizoid MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 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. Yes, but it doesn't matter --- if the tree changes under "cp -a" command, no one guarantees you what you get. int fis_hardlink(int handle1, int handle 2); Is another possibility but it can't detect hardlinked symlinks. Mikulas - 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/