[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <uboc64fpwzcs4phm2xppyvuf3h5clkijbiahsb2wd2vah3po5q@dnzh7ir6inqz>
Date: Fri, 21 Nov 2025 11:48:45 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan@...nel.org>, Yuwen Chen <ywen.chen@...mail.com>,
Richard Chang <richardycc@...gle.com>, Brian Geffon <bgeffon@...gle.com>,
Fengyu Lian <licayy@...look.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-block@...r.kernel.org
Subject: Re: [RFC PATCHv5 2/6] zram: add writeback batch size device attr
On (25/11/21 00:21), Sergey Senozhatsky wrote:
> +static ssize_t writeback_batch_size_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t len)
> +{
> + struct zram *zram = dev_to_zram(dev);
> + u32 val;
> + ssize_t ret = -EINVAL;
> +
> + if (kstrtouint(buf, 10, &val))
> + return ret;
> +
> + if (!val)
> + val = 1;
> +
> + down_read(&zram->init_lock);
> + zram->wb_batch_size = val;
> + up_read(&zram->init_lock);
> + ret = len;
> +
> + return ret;
> +}
JFI, as was suggested by Andrew in v4 thread, this should use write
lock.
Powered by blists - more mailing lists