> For now, we don't track RAM pages using memattr infrastructure. This is > because, > memattr infrastructure is not enough. i.e., while the page is getting > tracked using memattr infrastructure,
> potentially the page can get > freed(a bug that we need to catch, to avoid attribute aliasing). That would be a bug in the caller. But anybody who sets non standard attributes should go through memattr first. The only exception is /dev/mem -- not sure how to handle this best. Perhaps only allow memattr for non memory for there. -Andi -- 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/
