Andreas Dilger wrote:
The kernel doesn't necessarily have to clear the fields. The per-field
valid flag would determine is that field had valid data or garbage.
You cannot leak kernel memory content. Either you clear the field or,
in the code which actually copies the data to userlevel, you copy again
field by field. The latter is far too slow. So you better clear all
fields.
You can easily leave out the :ex=*** part of LS_COLORS.
Tell that to every distro maintainer, and/or try to convince the upstream
"ls" maintainers to change this. :-)
Why? Tell this to people who are affected.
It isn't just to fix the ls --color problem. There are lots of other
apps that need some stat fields and not others.
Name them. I've asked for it before and got the answer "it's mainly
ls". Now ls is debunked. So, provide more evidence that the
getdirentplus support is needed.
Also, implementing
the compatibility support for this (statlite->stat(), flags=$all_valid)
is trivial, if potentially less performant (though no worse than today).
We're not talking about statlite. The ls case is about getdirentplus.
I fail to see evidence that it is really needed.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
