From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kernel-team <kernel-team@lge.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] zram: fix null dereference of handle
Date: Wed, 20 Sep 2017 15:28:21 +0900 [thread overview]
Message-ID: <20170920062821.GC6298@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170920055125.GB9428@bbox>
Hello,
On (09/20/17 14:51), Minchan Kim wrote:
> On Tue, Sep 19, 2017 at 07:21:25PM +0900, Sergey Senozhatsky wrote:
> > Minchan,
> >
> > I just ran across it [because I had a bug to analize where this
> > part was involved]. I'd really prefer the kernel to BUG_ON immediately
> > instead of dying in agony.
> >
> > can we, please, return BUG_ON() back?
> >
> > there is no point in trying to save the kernel once it did that type
> > of violation.
>
> I agree. If it happens, it would corrupt other user's buffer which ends
> up leaking some private data from others so there is pointless to keep
> system alive to debug it.
thanks!
yep, I guess we are also potentially looking at __zs_map_object()
preempting zsmalloc in normal context, which would overwrite
area->vm_addr from IRQ, map it, use it, unmap it in __zs_unmap_object().
and then resumed normal context will attempt to use unmapped area->vm_addr,
I suppose.
> Do you mind sending a formal patch?
sure, will do.
-ss
next prev parent reply other threads:[~2017-09-20 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 10:21 Sergey Senozhatsky
2017-09-19 10:38 ` BUG_ON when zsmalloc from IRQ (was zram: fix null dereference of handle) Sergey Senozhatsky
2017-09-20 5:51 ` [PATCH] zram: fix null dereference of handle Minchan Kim
2017-09-20 6:28 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-19 2:34 Minchan Kim
2017-09-19 5:39 ` Sergey Senozhatsky
2017-09-19 6:59 ` Minchan Kim
2017-09-19 10:15 ` Sergey Senozhatsky
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=20170920062821.GC6298@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®