On 20 January 2016 at 05:00, Kirill A. Shutemov <kirill@xxxxxxxxxxxxx> wrote: > I doubt it can be very useful as it's unreliable: if two stacks are > allocated end-to-end (which is not good idea, but still) it can only > report [stack:XXX] for the first one as they are merged into one VMA. > Any other anon VMA merged with the stack will be also claimed as stack, > which is not always correct. It is quite uncommon because you will always have an intervening guard page that separates the two stack vmas. To have the vmas merge, you will have to disable guard pages which is an even worse idea. A more relevant argument about its unreliability is context changes due to makecontext/setcontext, which could momentarily show the heap or some other arbitrary vma as a stack. Siddhesh -- http://siddhesh.in -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>