Re: [PATCH 1/5] WIP: Add syscall unlinkat_s (currently x86* only)

From: Alexander Holler
Date: Wed Feb 04 2015 - 08:08:00 EST


Am 04.02.2015 um 13:50 schrieb Alexander Holler:
Am 04.02.2015 um 13:42 schrieb Alexander Holler:
Am 04.02.2015 um 13:22 schrieb Alexander Holler:
Am 04.02.2015 um 13:07 schrieb Lukáš Czerner:

The fact is that the current patches are useless for anything other
than proof-of-concept. Now you know more that needs to be done or

That's wrong. The patches already work. If you delete a file which isn't
in use by something else, the current contents will be wiped on
traditional harddrives. I assume that already fulfills more than 50% of
use cases of ordinary people.

thought about, but if you're not willing to do the work, then please
stop complaining about "high towers". I am not a maintainer and I
thinks that the feedback you've got is entirely reasonable. Take it
as you will.

One more thing, can I ask you what were your expectations when
posting those patches ?

I've posted them for other users which are happy with what I've
explained above. Besides requesting an API which makes such a simple
solution, in contrast to the the 's' bit, possible.

To be more precise: How do you add something like EXT2_IOC_[SG[ETFLAGS
to vfat or one of the dozens other filesystems which don't know about
linux-specific flags? I don't see a way to do that, so there's only
unlinkat() left.

Or to be give an actual use case, mount a (v)fat formatted usb-stick,
-hdd or mmc, delete a file with the patches I offered, unmount it, try
to find the contents of the deleted file at device-level (e.g. by
grepping the partition).

Maybe I should mention that I've tried it with bug reports instead patches before. Beeing aware that I might be unable to write perfect patches with the resources I'm able or willing to spend.

I just needed some days until the one for ext4 was closed, leaving no hope that it might become fixed without trying it myself.

Alexander Holler

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