From: Greg KH <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Steven Allen <steven@stebalien.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] zram: restrict add/remove attributes to root only
Date: Sun, 4 Dec 2016 12:28:20 +0100 [thread overview]
Message-ID: <20161204112820.GA24757@kroah.com> (raw)
In-Reply-To: <20161204105208.GA592@tigerII.localdomain>
On Sun, Dec 04, 2016 at 07:52:08PM +0900, Sergey Senozhatsky wrote:
> On (12/04/16 11:28), Greg KH wrote:
> > On Sun, Dec 04, 2016 at 11:35:15AM +0900, Sergey Senozhatsky wrote:
> [..]
>
> > Why can't a normal user read the attribute? Does a read actually modify
> > something?
>
> yes, it does.
Oh that's totally and completely broken then.
Reading from a sysfs file should NEVER cause side affects to the system.
Please fix up this api.
> reading from a hot_add file creates a new zram device and returns a new
> device's device_id. not initialized device (so it does not eat the memory
> for handle table, etc.), but with its own set of sysfs attrs, etc. which
> consumes memory after all. so a 'normal' user, doing a simple read from a
> hot_add file in a loop just for fun, can create a lot of devices and,
> quite likely, cause some troubles (as reported by Steven Allen).
Please switch this to be a char device node if you wish to "write and
get a device handle back". I don't know how I missed that in the
original api review, sorry about that.
For now, you need to document the heck out of this in the attribute
declaration that this is what is going on. Otherwise someone like me
will come along and "fix up" the file to use ATTR_RO again in the
future and you will have the same problem again.
thanks,
greg k-h
next prev parent reply other threads:[~2016-12-04 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 2:35 [PATCH] zram: restrict add/remove attributes to root only Sergey Senozhatsky
2016-12-04 10:28 ` Greg KH
2016-12-04 10:52 ` Sergey Senozhatsky
2016-12-04 11:28 ` Greg KH [this message]
2016-12-04 11:41 ` Sergey Senozhatsky
2016-12-04 11:55 ` Greg KH
2016-12-04 12:08 ` Sergey Senozhatsky
2016-12-04 12:49 ` 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=20161204112820.GA24757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@vger.kernel.org \
--cc=steven@stebalien.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