[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191108153543.GC99567@google.com>
Date: Fri, 8 Nov 2019 10:35:43 -0500
From: Joel Fernandes <joel@...lfernandes.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-kernel@...r.kernel.org,
Nicolas Geoffray <ngeoffray@...gle.com>,
kernel-team@...roid.com, Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>,
linux-kselftest@...r.kernel.org, linux-mm@...ck.org,
Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH 1/2] memfd: Fix COW issue on MAP_PRIVATE and
F_SEAL_FUTURE_WRITE mappings
On Thu, Nov 07, 2019 at 10:33:08PM -0800, Christoph Hellwig wrote:
> > - * Since the F_SEAL_FUTURE_WRITE seals allow for a MAP_SHARED
> > - * read-only mapping, take care to not allow mprotect to revert
> > - * protections.
> > + * Since an F_SEAL_FUTURE_WRITE sealed memfd can be mapped as
> > + * MAP_SHARED and read-only, take care to not allow mprotect to
> > + * revert protections on such mappings. Do this only for shared
> > + * mappings. For private mappings, don't need to mask VM_MAYWRITE
>
> This adds an > 80 char line.
Oh, true. Sorry. Andrew I hate to ask you but since you took the patch
already, could you just the comment for the character limit in the one
you applied?
thanks,
- Joel
Powered by blists - more mailing lists