On Thu, 2018-12-06 at 15:08 -0800, Nadav Amit wrote:
> > On Dec 6, 2018, at 12:17 PM, Andy Lutomirski wrote:
> >
> > On Thu, Dec 6, 2018 at 11:39 AM Nadav Amit wrote:
> > > > On Dec 6, 2018, at 11:19 AM, Andy Lutomirski wrote:
> > > >
> > > > On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wro
> On Dec 6, 2018, at 12:17 PM, Andy Lutomirski wrote:
>
> On Thu, Dec 6, 2018 at 11:39 AM Nadav Amit wrote:
>>> On Dec 6, 2018, at 11:19 AM, Andy Lutomirski wrote:
>>>
>>> On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrot
On Thu, Dec 6, 2018 at 12:20 PM Edgecombe, Rick P
wrote:
>
> On Thu, 2018-12-06 at 11:19 -0800, Andy Lutomirski wrote:
> > On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
> > >
> > > On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
> > > > > If we are going to unmap the line
On Thu, 2018-12-06 at 11:19 -0800, Andy Lutomirski wrote:
> On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
> >
> > On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
> > > > If we are going to unmap the linear alias, why not do it at vmalloc()
> > > > time rather than vfree()
On Thu, Dec 6, 2018 at 11:39 AM Nadav Amit wrote:
>
> > On Dec 6, 2018, at 11:19 AM, Andy Lutomirski wrote:
> >
> > On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
> >> On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
> If we are going to unmap the linear alias, why no
> On Dec 6, 2018, at 11:19 AM, Andy Lutomirski wrote:
>
> On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
>> On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
If we are going to unmap the linear alias, why not do it at vmalloc()
time rather than vfree() time?
>>>
On Thu, 6 Dec 2018 at 20:30, Will Deacon wrote:
>
> On Thu, Dec 06, 2018 at 08:23:20PM +0100, Ard Biesheuvel wrote:
> > On Thu, 6 Dec 2018 at 20:21, Andy Lutomirski wrote:
> > >
> > > On Thu, Dec 6, 2018 at 11:04 AM Ard Biesheuvel
> > > wrote:
> > > >
> > > > On Thu, 6 Dec 2018 at 19:54, Andy Lu
On Thu, Dec 06, 2018 at 08:23:20PM +0100, Ard Biesheuvel wrote:
> On Thu, 6 Dec 2018 at 20:21, Andy Lutomirski wrote:
> >
> > On Thu, Dec 6, 2018 at 11:04 AM Ard Biesheuvel
> > wrote:
> > >
> > > On Thu, 6 Dec 2018 at 19:54, Andy Lutomirski wrote:
> > > >
> >
> > > > That’s not totally nuts. Do
On Thu, 6 Dec 2018 at 20:21, Andy Lutomirski wrote:
>
> On Thu, Dec 6, 2018 at 11:04 AM Ard Biesheuvel
> wrote:
> >
> > On Thu, 6 Dec 2018 at 19:54, Andy Lutomirski wrote:
> > >
>
> > > That’s not totally nuts. Do we ever have code that expects __va() to
> > > work on module data? Perhaps crypt
On Thu, Dec 6, 2018 at 11:04 AM Ard Biesheuvel
wrote:
>
> On Thu, 6 Dec 2018 at 19:54, Andy Lutomirski wrote:
> >
> > That’s not totally nuts. Do we ever have code that expects __va() to
> > work on module data? Perhaps crypto code trying to encrypt static
> > data because our APIs don’t unders
On Thu, Dec 6, 2018 at 11:01 AM Tycho Andersen wrote:
>
> On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
> > > If we are going to unmap the linear alias, why not do it at vmalloc()
> > > time rather than vfree() time?
> >
> > That’s not totally nuts. Do we ever have code that exp
On Thu, 6 Dec 2018 at 19:54, Andy Lutomirski wrote:
>
> > On Dec 5, 2018, at 11:29 PM, Ard Biesheuvel
> > wrote:
> >
> >> On Thu, 6 Dec 2018 at 00:16, Andy Lutomirski wrote:
> >>
> >>> On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
> >>>
> On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy
On Thu, Dec 06, 2018 at 10:53:50AM -0800, Andy Lutomirski wrote:
> > On Dec 5, 2018, at 11:29 PM, Ard Biesheuvel
> > wrote:
> >
> >> On Thu, 6 Dec 2018 at 00:16, Andy Lutomirski wrote:
> >>
> >>> On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
> >>>
> On Tue, Dec 04, 2018 at 12:09:49PM -
> On Dec 5, 2018, at 11:29 PM, Ard Biesheuvel wrote:
>
>> On Thu, 6 Dec 2018 at 00:16, Andy Lutomirski wrote:
>>
>>> On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
>>>
On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy Lutomirski wrote:
On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
On Thu, Dec 06, 2018 at 08:29:03AM +0100, Ard Biesheuvel wrote:
> On Thu, 6 Dec 2018 at 00:16, Andy Lutomirski wrote:
> >
> > On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
> > >
> > > On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy Lutomirski wrote:
> > > > On Tue, Dec 4, 2018 at 12:02 PM Edge
On Thu, 6 Dec 2018 at 00:16, Andy Lutomirski wrote:
>
> On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
> >
> > On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy Lutomirski wrote:
> > > On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
> > > wrote:
> > > >
> > > > On Tue, 2018-12-04 at 16:03 +000
On Wed, Dec 5, 2018 at 3:41 AM Will Deacon wrote:
>
> On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy Lutomirski wrote:
> > On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
> > wrote:
> > >
> > > On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
> > > > On Mon, Dec 03, 2018 at 05:43:11PM -080
On Tue, Dec 04, 2018 at 12:09:49PM -0800, Andy Lutomirski wrote:
> On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
> wrote:
> >
> > On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
> > > On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
> > > > > On Nov 27, 2018, at 4:07 PM, Rick
> On Dec 4, 2018, at 5:45 PM, Edgecombe, Rick P
> wrote:
>
> On Tue, 2018-12-04 at 16:53 -0800, Nadav Amit wrote:
>>> On Dec 4, 2018, at 4:29 PM, Edgecombe, Rick P
>>> wrote:
>>>
>>> On Tue, 2018-12-04 at 16:01 -0800, Nadav Amit wrote:
> On Dec 4, 2018, at 3:51 PM, Edgecombe, Rick P <
> On Dec 4, 2018, at 3:52 PM, Edgecombe, Rick P
> wrote:
>
>> On Tue, 2018-12-04 at 12:09 -0800, Andy Lutomirski wrote:
>> On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
>> wrote:
>>>
On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
On Mon, Dec 03, 2018 at 05:43:11PM -0800
On Tue, 2018-12-04 at 16:53 -0800, Nadav Amit wrote:
> > On Dec 4, 2018, at 4:29 PM, Edgecombe, Rick P
> > wrote:
> >
> > On Tue, 2018-12-04 at 16:01 -0800, Nadav Amit wrote:
> > > > On Dec 4, 2018, at 3:51 PM, Edgecombe, Rick P <
> > > > rick.p.edgeco...@intel.com>
> > > > wrote:
> > > >
> > >
> On Dec 4, 2018, at 5:09 PM, Edgecombe, Rick P
> wrote:
>
> On Tue, 2018-12-04 at 14:48 -0800, Nadav Amit wrote:
>>> On Dec 4, 2018, at 11:48 AM, Andy Lutomirski wrote:
>>>
>>> On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
> On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
>
On Tue, 2018-12-04 at 14:48 -0800, Nadav Amit wrote:
> > On Dec 4, 2018, at 11:48 AM, Andy Lutomirski wrote:
> >
> > On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
> > > > On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
> > > >
> > > > On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
>
> On Dec 4, 2018, at 4:29 PM, Edgecombe, Rick P
> wrote:
>
> On Tue, 2018-12-04 at 16:01 -0800, Nadav Amit wrote:
>>> On Dec 4, 2018, at 3:51 PM, Edgecombe, Rick P
>>> wrote:
>>>
>>> On Tue, 2018-12-04 at 12:36 -0800, Nadav Amit wrote:
> On Dec 4, 2018, at 12:02 PM, Edgecombe, Rick P <
>>>
On Tue, 2018-12-04 at 16:01 -0800, Nadav Amit wrote:
> > On Dec 4, 2018, at 3:51 PM, Edgecombe, Rick P
> > wrote:
> >
> > On Tue, 2018-12-04 at 12:36 -0800, Nadav Amit wrote:
> > > > On Dec 4, 2018, at 12:02 PM, Edgecombe, Rick P <
> > > > rick.p.edgeco...@intel.com>
> > > > wrote:
> > > >
> > >
> On Dec 4, 2018, at 3:51 PM, Edgecombe, Rick P
> wrote:
>
> On Tue, 2018-12-04 at 12:36 -0800, Nadav Amit wrote:
>>> On Dec 4, 2018, at 12:02 PM, Edgecombe, Rick P
>>> wrote:
>>>
>>> On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Ami
On Tue, 2018-12-04 at 12:09 -0800, Andy Lutomirski wrote:
> On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
> wrote:
> >
> > On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
> > > On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
> > > > > On Nov 27, 2018, at 4:07 PM, Rick Edgeco
> On Dec 4, 2018, at 3:27 PM, Andy Lutomirski wrote:
>
>
>
>
> On Dec 4, 2018, at 2:48 PM, Nadav Amit wrote:
>
>>> On Dec 4, 2018, at 11:48 AM, Andy Lutomirski wrote:
>>>
>>> On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
> On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
>
On Dec 4, 2018, at 2:48 PM, Nadav Amit wrote:
>> On Dec 4, 2018, at 11:48 AM, Andy Lutomirski wrote:
>>
>> On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
>> On Nov
> On Dec 4, 2018, at 11:48 AM, Andy Lutomirski wrote:
>
> On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
>>> On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
>>>
>>> On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
> On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> wrote:
>
> On Dec 4, 2018, at 12:02 PM, Edgecombe, Rick P
> wrote:
>
> On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
>> On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
wrote:
Since vfree will lazily flush the TLB, but n
On Tue, Dec 4, 2018 at 12:02 PM Edgecombe, Rick P
wrote:
>
> On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
> > On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
> > > > On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> > > > wrote:
> > > >
> > > > Since vfree will lazily flush the T
On Tue, 2018-12-04 at 16:03 +, Will Deacon wrote:
> On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
> > > On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> > > wrote:
> > >
> > > Since vfree will lazily flush the TLB, but not lazily free the underlying
> > > pages,
> > > it often leav
On Tue, Dec 4, 2018 at 11:45 AM Nadav Amit wrote:
>
> > On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
> >
> > On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
> >>> On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> >>> wrote:
> >>>
> >>> Since vfree will lazily flush the TLB, but not lazily
> On Dec 4, 2018, at 10:56 AM, Andy Lutomirski wrote:
>
> On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
>>> On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
>>> wrote:
>>>
>>> Since vfree will lazily flush the TLB, but not lazily free the underlying
>>> pages,
>>> it often leaves stale TLB ent
On Mon, Dec 3, 2018 at 5:43 PM Nadav Amit wrote:
>
> > On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> > wrote:
> >
> > Since vfree will lazily flush the TLB, but not lazily free the underlying
> > pages,
> > it often leaves stale TLB entries to freed pages that could get re-used.
> > This is
>
On Mon, Dec 03, 2018 at 05:43:11PM -0800, Nadav Amit wrote:
> > On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> > wrote:
> >
> > Since vfree will lazily flush the TLB, but not lazily free the underlying
> > pages,
> > it often leaves stale TLB entries to freed pages that could get re-used.
> > T
> On Nov 27, 2018, at 4:07 PM, Rick Edgecombe
> wrote:
>
> Since vfree will lazily flush the TLB, but not lazily free the underlying
> pages,
> it often leaves stale TLB entries to freed pages that could get re-used. This
> is
> undesirable for cases where the memory being freed has special pe
It looks like this new flag is in linux-next now. As I am reading it, these
architectures have a module_alloc that uses some sort of executable flag and
are not using the default module_alloc which is already covered, and so may need
it plugged in:
arm
arm64
parisc
s390
unicore32
Thanks,
Rick
On
Since vfree will lazily flush the TLB, but not lazily free the underlying pages,
it often leaves stale TLB entries to freed pages that could get re-used. This is
undesirable for cases where the memory being freed has special permissions such
as executable.
Having callers flush the TLB after callin
40 matches
Mail list logo
