Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754464AbbGFIvN (ORCPT ); Mon, 6 Jul 2015 04:51:13 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:34153 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754427AbbGFIvK (ORCPT ); Mon, 6 Jul 2015 04:51:10 -0400 From: Andrey Vagin To: linux-kernel@vger.kernel.org Cc: linux-api@vger.kernel.org, Andrey Vagin , Oleg Nesterov , Andrew Morton , Cyrill Gorcunov , Pavel Emelyanov , Roger Luethi , Arnd Bergmann , Arnaldo Carvalho de Melo , David Ahern , Andy Lutomirski , Pavel Odintsov Subject: [PATCH 14/24] task_diag: add a marcos to enumirate memory mappings Date: Mon, 6 Jul 2015 11:47:15 +0300 Message-Id: <1436172445-6979-15-git-send-email-avagin@openvz.org> X-Mailer: git-send-email 2.1.0 In-Reply-To: <1436172445-6979-1-git-send-email-avagin@openvz.org> References: <1436172445-6979-1-git-send-email-avagin@openvz.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 33 This macros will help users to use this interface. v2: Fix task_diag_for_each_vma to work with libnl // David Ahern Signed-off-by: Andrey Vagin --- include/uapi/linux/task_diag.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/include/uapi/linux/task_diag.h b/include/uapi/linux/task_diag.h index 73d33c8..9e4c3c4 100644 --- a/include/uapi/linux/task_diag.h +++ b/include/uapi/linux/task_diag.h @@ -143,6 +143,11 @@ static inline struct task_diag_vma_stat *task_diag_vma_stat(struct task_diag_vma return ((void *)vma) + vma->stat_off; } +#define task_diag_for_each_vma(vma, attr) \ + for (vma = nla_data(attr); \ + (void *) vma < nla_data(attr) + nla_len(attr); \ + vma = (void *) vma + vma->vma_len) + #define TASK_DIAG_DUMP_ALL 0 #define TASK_DIAG_DUMP_CHILDREN 1 -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/