All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, stable@vger.kernel.org,
	sergey.senozhatsky.work@gmail.com, ngupta@vflare.org,
	jglisse@redhat.com
Subject: Re: + zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch added to -mm tree
Date: Thu, 18 Apr 2019 11:56:53 +0900	[thread overview]
Message-ID: <20190418025653.GA39673@google.com> (raw)
In-Reply-To: <20190416235350.NIVru%akpm@linux-foundation.org>

On Tue, Apr 16, 2019 at 04:53:50PM -0700, akpm@linux-foundation.org wrote:
> 
> The patch titled
>      Subject: zram: pass down the bvec we need to read into in the work struct
> has been added to the -mm tree.  Its filename is
>      zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch
> 
> This patch should soon appear at
>     http://ozlabs.org/~akpm/mmots/broken-out/zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch
> and later at
>     http://ozlabs.org/~akpm/mmotm/broken-out/zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> 
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
> 
> ------------------------------------------------------
> From: Jérôme Glisse <jglisse@redhat.com>
> Subject: zram: pass down the bvec we need to read into in the work struct
> 
> When scheduling work item to read page we need to pass down the proper
> bvec struct which points to the page to read into.  Before this patch it
> uses a randomly initialized bvec (only if PAGE_SIZE != 4096) which is
> wrong.
> 
> Note that without this patch on arch/kernel where PAGE_SIZE != 4096
> userspace could read random memory through a zram block device (thought
> userspace probably would have no control on the address being read).
> 
> Link: http://lkml.kernel.org/r/20190408183219.26377-1-jglisse@redhat.com
> Signed-off-by: Jérôme Glisse <jglisse@redhat.com>
> Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Nitin Gupta <ngupta@vflare.org>
> Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

Thanks for the nice catch, Jerome!
That sync/async read code in zram is really mess. :(

Acked-by: Minchan Kim <minchan@kernel.org>

      reply	other threads:[~2019-04-18  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 23:53 + zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch added to -mm tree akpm
2019-04-18  2:56 ` Minchan Kim [this message]

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=20190418025653.GA39673@google.com \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jglisse@redhat.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=stable@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 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.