On Thu, 21 Jun 2007, Ian McDonald wrote:
>
> It depends on the purpose of DEBUG_RODATA. If DEBUG_RODATA was for
> security reasons then I agree, but it seems to be more to catch
> accidental writes.
Well, I'd say that it is *one* tool for debugging.
Now, Kprobes is another tool - and I'm just saying that I don't see why
you should really expect to break one tool with the other. They take
different approaches.
And yes, sometimes debugging *does* change what it debugs. In timing, if
nothing else, but also in the kinds of things you can do. For example, we
don't allow slab redzoning on data structures that have alignment
restrictions not compatible with the redzoning, and I'd argue that this is
more of the same: we just should not do DEBUG_RODATA if you expect to
change read-only data.
There's just no *point*.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
