linux-kernel - Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200707162023.04646.a1426z@gawab.com>
Date:	Mon, 16 Jul 2007 20:23:04 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	Jörn Engel <joern@...fs.org>,
	Satyam Sharma <satyam.sharma@...il.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Hardlink Pitfalls (was: Patches for REALLY TINY 386 kernels)

Jörn Engel wrote:
> On Mon, 16 July 2007 22:14:41 +0530, Satyam Sharma wrote:
> > On 7/16/07, Al Boldi <a1426z@...ab.com> wrote:
> > >Satyam Sharma wrote:
> > >> Or just "cp -al" to create multiple trees at (almost) no disk cost
> > >> that won't interfere with each other in any way, and makes the
> > >> development process / generating patchsets trifle easier as well ...
> > >
> > >That would be correct if hardlinks would actually do a CoW on modify,
> > >instead
> > >of misleading the user into thinking he is modifying an independent
> > > file.
> >
> > "patch" already handles this correctly ... and
> > backupcopy=auto,breakhardlink in vim (and something similar in other
> > editors I presume)
>
> Yet even a single program failing to break the link will leave you with
> a mess to sort out.

No kidding!

> The only place that can ensure to always break the
> link is the kernel.  Which is why I wrote the cowlink patches some years
> back.

Can you post a patch against 2.6.22?

> The still need a lot of love to be merge-ready.  But I do use them on a
> daily basis.

Well, if the patch is lean and optional and runtime configurable, then they 
should definitely be considered for inclusion.


Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/