From: Igor Stoppa <igor.stoppa@huawei.com>
To: J Freyensee <why2jjj.linux@gmail.com>,
Matthew Wilcox <willy@infradead.org>
Cc: <david@fromorbit.com>, <rppt@linux.vnet.ibm.com>,
<keescook@chromium.org>, <mhocko@kernel.org>,
<labbott@redhat.com>, <linux-security-module@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH 4/8] struct page: add field for vm_struct
Date: Thu, 15 Mar 2018 11:38:36 +0200 [thread overview]
Message-ID: <6924c919-dbfb-a9f6-748a-0bbfe8d876b1@huawei.com> (raw)
In-Reply-To: <7b18521c-539b-2ba1-823e-e83be071c13f@gmail.com>
On 14/03/18 19:43, J Freyensee wrote:
> On 3/13/18 3:00 PM, Matthew Wilcox wrote:
[...]
>>> Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> Igor, do you mind sticking these tags on the files that have spent some
> time reviewing a revision of your patchset (like the Reviewed-by: tags I
> provided last revision?)
Apologies, that was not intentional, I forgot it.
I will do it, although most of the files will now change so much that I
am not sure what will survive, beside this patch, in the form that you
reviewed.
I suppose the Review-by tag drops, if the patch changes.
--
igor
WARNING: multiple messages have this Message-ID (diff)
From: igor.stoppa@huawei.com (Igor Stoppa)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 4/8] struct page: add field for vm_struct
Date: Thu, 15 Mar 2018 11:38:36 +0200 [thread overview]
Message-ID: <6924c919-dbfb-a9f6-748a-0bbfe8d876b1@huawei.com> (raw)
In-Reply-To: <7b18521c-539b-2ba1-823e-e83be071c13f@gmail.com>
On 14/03/18 19:43, J Freyensee wrote:
> On 3/13/18 3:00 PM, Matthew Wilcox wrote:
[...]
>>> Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> Igor, do you mind sticking these tags on the files that have spent some
> time reviewing a revision of your patchset (like the Reviewed-by: tags I
> provided last revision?)
Apologies, that was not intentional, I forgot it.
I will do it, although most of the files will now change so much that I
am not sure what will survive, beside this patch, in the form that you
reviewed.
I suppose the Review-by tag drops, if the patch changes.
--
igor
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Igor Stoppa <igor.stoppa@huawei.com>
To: J Freyensee <why2jjj.linux@gmail.com>,
Matthew Wilcox <willy@infradead.org>
Cc: david@fromorbit.com, rppt@linux.vnet.ibm.com,
keescook@chromium.org, mhocko@kernel.org, labbott@redhat.com,
linux-security-module@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 4/8] struct page: add field for vm_struct
Date: Thu, 15 Mar 2018 11:38:36 +0200 [thread overview]
Message-ID: <6924c919-dbfb-a9f6-748a-0bbfe8d876b1@huawei.com> (raw)
In-Reply-To: <7b18521c-539b-2ba1-823e-e83be071c13f@gmail.com>
On 14/03/18 19:43, J Freyensee wrote:
> On 3/13/18 3:00 PM, Matthew Wilcox wrote:
[...]
>>> Signed-off-by: Igor Stoppa <igor.stoppa@huawei.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> Igor, do you mind sticking these tags on the files that have spent some
> time reviewing a revision of your patchset (like the Reviewed-by: tags I
> provided last revision?)
Apologies, that was not intentional, I forgot it.
I will do it, although most of the files will now change so much that I
am not sure what will survive, beside this patch, in the form that you
reviewed.
I suppose the Review-by tag drops, if the patch changes.
--
igor
next prev parent reply other threads:[~2018-03-15 9:38 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 21:45 [RFC PATCH v19 0/8] mm: security: ro protection for dynamic data Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 1/8] genalloc: track beginning of allocations Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 2/8] Add label to genalloc.rst for cross reference Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 3/8] genalloc: selftest Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 4/8] struct page: add field for vm_struct Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 22:00 ` Matthew Wilcox
2018-03-13 22:00 ` Matthew Wilcox
2018-03-14 17:43 ` J Freyensee
2018-03-14 17:43 ` J Freyensee
2018-03-15 9:38 ` Igor Stoppa [this message]
2018-03-15 9:38 ` Igor Stoppa
2018-03-15 9:38 ` Igor Stoppa
2018-03-15 18:51 ` J Freyensee
2018-03-15 18:51 ` J Freyensee
2018-03-13 21:45 ` [PATCH 5/8] Protectable Memory Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-14 12:15 ` Matthew Wilcox
2018-03-14 12:15 ` Matthew Wilcox
2018-03-14 13:02 ` Igor Stoppa
2018-03-14 13:02 ` Igor Stoppa
2018-03-14 13:02 ` Igor Stoppa
2018-03-14 17:40 ` J Freyensee
2018-03-14 17:40 ` J Freyensee
2018-03-14 17:40 ` J Freyensee
2018-03-13 21:45 ` [PATCH 6/8] Pmalloc selftest Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-14 12:25 ` Matthew Wilcox
2018-03-14 12:25 ` Matthew Wilcox
2018-03-25 1:32 ` Igor Stoppa
2018-03-25 1:32 ` Igor Stoppa
2018-03-25 1:32 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 7/8] lkdtm: crash on overwriting protected pmalloc var Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` [PATCH 8/8] Documentation for Pmalloc Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-13 21:45 ` Igor Stoppa
2018-03-14 11:21 ` [RFC PATCH v19 0/8] mm: security: ro protection for dynamic data Igor Stoppa
2018-03-14 11:21 ` Igor Stoppa
2018-03-14 11:21 ` Igor Stoppa
2018-03-14 11:56 ` Matthew Wilcox
2018-03-14 11:56 ` Matthew Wilcox
2018-03-14 12:55 ` Igor Stoppa
2018-03-14 12:55 ` Igor Stoppa
2018-03-14 12:55 ` Igor Stoppa
2018-03-14 13:04 ` Matthew Wilcox
2018-03-14 13:04 ` Matthew Wilcox
2018-03-14 16:11 ` Igor Stoppa
2018-03-14 16:11 ` Igor Stoppa
2018-03-14 16:11 ` Igor Stoppa
2018-03-14 17:33 ` Matthew Wilcox
2018-03-14 17:33 ` Matthew Wilcox
2018-03-15 13:43 ` Igor Stoppa
2018-03-15 13:43 ` Igor Stoppa
2018-03-15 13:43 ` Igor Stoppa
2018-03-19 18:04 ` Igor Stoppa
2018-03-19 18:04 ` Igor Stoppa
2018-03-19 18:04 ` Igor Stoppa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6924c919-dbfb-a9f6-748a-0bbfe8d876b1@huawei.com \
--to=igor.stoppa@huawei.com \
--cc=david@fromorbit.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=why2jjj.linux@gmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.