linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Maurizio Lombardi <mlombard@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Chen Lin <chen45464546@163.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 Netdev <netdev@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: prevent page_frag_alloc() from corrupting the memory
Date: Mon, 11 Jul 2022 20:36:42 +0200	[thread overview]
Message-ID: <CAFL455mDtwo-g_eCzihoQeeVpzRHR6YfHHuRBLCTgt2kP64g2A@mail.gmail.com> (raw)
In-Reply-To: <CAKgT0Ue0j1-EF+X0miM4ZYQgJ7xLX79BwN58rqHcaEBzC6BBcg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

po 11. 7. 2022 v 20:23 odesílatel Alexander Duyck <alexander.duyck@gmail.com>
napsal:

> On Mon, Jul 11, 2022 at 9:17 AM Maurizio Lombardi <mlombard@redhat.com>
> wrote:
> >
> > po 11. 7. 2022 v 17:34 odesílatel Alexander Duyck
> > <alexander.duyck@gmail.com> napsal:
> > >
> > > Rather than forcing us to free the page it might be better to move the
> > > lines getting the size and computing the offset to the top of the "if
> > > (unlikely(offset < 0)) {" block. Then instead of freeing the page we
> > > could just return NULL and don't have to change the value of any
> > > fields in the page_frag_cache.
> > >
> > > That way a driver performing bad requests can't force us to start
> > > allocating and freeing pages like mad by repeatedly flushing the
> > > cache.
> > >
> >
> > I understand. On the other hand, if we free the cache page then the
> > next time __page_frag_cache_refill() runs it may be successful
> > at allocating the order=3 cache, the normal page_frag_alloc() behaviour
> will
> > therefore be restored.
>
> That is a big "maybe". My concern is that it will actually make memory
> pressure worse by forcing us to reduce the number of uses for a lower
> order page. One bad actor will have us flushing memory like mad so a
> guy expecting a small fragment may end up allocating 32K pages because
> someone else is trying to allocate them.
>
> I recommend we do not optimize for a case which this code was not
> designed for. Try to optimize for the standard case that most of the
> drivers are using. These drivers that are allocating higher order
> pages worth of memory should really be using alloc_pages. Using this
> to allocate pages over 4K in size is just a waste since they are not
> likely to see page reuse which is what this code expects to see.


Ok, thanks for the review, I will submit a V2 soon.

Maurizio

[-- Attachment #2: Type: text/html, Size: 2563 bytes --]

  reply	other threads:[~2022-07-11 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  7:52 Maurizio Lombardi
2022-07-11  9:02 ` Maurizio Lombardi
2022-07-11 15:34 ` Alexander Duyck
2022-07-11 16:17   ` Maurizio Lombardi
2022-07-11 18:23     ` Alexander Duyck
2022-07-11 18:36       ` Maurizio Lombardi [this message]
2022-07-13 14:58 Maurizio Lombardi
2022-07-13 15:01 ` Maurizio Lombardi

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=CAFL455mDtwo-g_eCzihoQeeVpzRHR6YfHHuRBLCTgt2kP64g2A@mail.gmail.com \
    --to=mlombard@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.duyck@gmail.com \
    --cc=chen45464546@163.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.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