From: Markus Elfring <Markus.Elfring@web.de>
To: Suren Baghdasaryan <surenb@google.com>,
linux-mm@kvack.org, kernel-janitors@vger.kernel.org,
kernel-team@android.com
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
David Hildenbrand <david@redhat.com>,
David Rientjes <rientjes@google.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Greg Thelen <gthelen@google.com>, Hugh Dickins <hughd@google.com>,
Jann Horn <jannh@google.com>, Jerome Glisse <jglisse@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Michal Hocko <mhocko@kernel.org>,
Michel Lespinasse <michel@lespinasse.org>,
Pasha Tatashin <tatashin@google.com>,
Peter Xu <peterx@redhat.com>,
Punit Agrawal <punit.agrawal@bytedance.com>,
Shakeel Butt <shakeelb@google.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [1/2] mm: lock a vma before stack expansion
Date: Sat, 8 Jul 2023 08:33:35 +0200 [thread overview]
Message-ID: <3b682e67-17c2-503d-0dbd-b0a9757f13c3@web.de> (raw)
In-Reply-To: <CAJuCfpEX8tXMKd7BKu7JOxhSfgeVnaerJ2db6PqfrScG5cUwig@mail.gmail.com>
>> Would you like to take any further information better into account
>> for subsequent patch variants?
>
> All feedback is appreciated.
Thanks for such a positive response.
> The comments you provided so far seem to
> be nice-to-haves but not critical enough to post a new version of the
> patch IMHO.
I guess that our dialogue can increase the probability for more desirable improvements.
I got used to point items out which can affect also the development process
for Linux software components.
It seems that some contributors stumble still on difficulties to handle
presented patch review approaches in more constructive ways.
> If something more substantial is found that requires a new
> version then I'll address your feedback there as well.
Will the chances grow to pick further recommendations, guidelines and
related change possibilities up?
Regards,
Markus
next prev parent reply other threads:[~2023-07-08 6:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 4:32 [PATCH 1/2] " Suren Baghdasaryan
2023-07-07 4:32 ` [PATCH 2/2] mm: lock newly mapped VMA which can be modified after it becomes visible Suren Baghdasaryan
2023-07-07 19:48 ` Liam R. Howlett
2023-07-07 20:15 ` Suren Baghdasaryan
2023-07-07 19:27 ` [PATCH 1/2] mm: lock a vma before stack expansion Andrew Morton
2023-07-07 20:03 ` Suren Baghdasaryan
2023-07-07 20:00 ` Markus Elfring
2023-07-07 20:03 ` Matthew Wilcox
2023-07-07 20:08 ` Suren Baghdasaryan
2023-07-08 5:55 ` [1/2] " Markus Elfring
2023-07-08 6:18 ` Suren Baghdasaryan
2023-07-08 6:33 ` Markus Elfring [this message]
2023-07-08 5:30 ` Markus Elfring
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=3b682e67-17c2-503d-0dbd-b0a9757f13c3@web.de \
--to=markus.elfring@web.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jglisse@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mhocko@kernel.org \
--cc=michel@lespinasse.org \
--cc=peterx@redhat.com \
--cc=punit.agrawal@bytedance.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=surenb@google.com \
--cc=tatashin@google.com \
--cc=vbabka@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox