Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5635004imu; Mon, 26 Nov 2018 03:18:35 -0800 (PST) X-Google-Smtp-Source: AFSGD/Xo/MgzpJolpI09j6XsqjNqr/A+3BO94MLEx4PCq7ZXKiCJi/tKsMhGUz89IB+9Upx76oHy X-Received: by 2002:a17:902:20c8:: with SMTP id v8mr8422670plg.319.1543231114989; Mon, 26 Nov 2018 03:18:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543231114; cv=none; d=google.com; s=arc-20160816; b=vqUnIu+3ltJrc8xo6/khFn14nxF6Dz5XbzBp7hmF+6b1nk2Pud5BCs5rAd4kVygRYx Gl3nBk71g6+OoAyv0mtzP4IkvuG8Mja63QHIrriyYNvYt0tN1OnBbswVHPoB/W3/a4yA pmKwc5lT6oQkCd2dFxofdUp9830EpBEtejdI8y4BktV3eXnEsmspTm+8shGJms6ErlSA Wb5cXxS/jZDnxbuDlER0Dob5yXJF6i2C19GoLUow1ntkkJWUrg7lbwxOCwS7i4Qm9yb9 TH3rW3GjmnsEOHQQnHOFoIbPjfSKEeRPdBZa6ERefZ9iDYiEEpV6/RshWe6MbRaMWSos vN3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=QRPhF7esmKeHDtA3VO2hNbaCYy9HKa7mb/2PvXBPMmo=; b=aatgachiyvMEnNN5jEB+7OGAso+w57IoYUMC2PlNS8yz+qmJdgAQicR9aCrQzfZeVQ OttVt/SAFrLka0PgRHfNtKosFYTrkUQmZjPETydUNI7PqnVUJT83230j3AY5z4u4b0hT o2HwqFnFiBaw14cRPTPVVE9JZynIJtSxJqMxVDIpOpmkXzwdltNC9MWLCp22Buwh7OTN gGUtOjYPwDvTwLBiG4uOSU1/eQJiUmgkqA//zltbwRGMn8xMIsAazD2c+NYz+q8hcQlT jK4hKXmKKzTpf1m+DSYE0X6cAmfktSibZ50mmdsQJ6AmzM6SfS0f9kloJtOvwD1/Z/sn GUzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=igZTnqeE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o89si1454921pfk.223.2018.11.26.03.18.20; Mon, 26 Nov 2018 03:18:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=igZTnqeE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730176AbeKZVzT (ORCPT + 99 others); Mon, 26 Nov 2018 16:55:19 -0500 Received: from mail.kernel.org ([198.145.29.99]:37856 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728901AbeKZVzS (ORCPT ); Mon, 26 Nov 2018 16:55:18 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E412620817; Mon, 26 Nov 2018 11:01:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543230093; bh=9QskiBcTestU6n0IchVKPNBuV76G4de3ikBy4EvsKVI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=igZTnqeE6imyXDmZl6ejmGiOH1BmOm711Y4OPTUg55X5Bp58KNjv8TNU+N3ZMa9Um GBFSJMhMGyhKphhSeIA49SdDFaOdQZpSOKBvLnAjGnJeTxu7Je+F39vCdIq2sUJZVk XDqpUxoXLzd70JLCYaPB9gbUsQzf2K88deYu4tjc= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Sergey Senozhatsky , Hannes Reinecke , Howard Chen , Minchan Kim , Sasha Levin Subject: [PATCH 4.14 40/62] zram: close udev startup race condition as default groups Date: Mon, 26 Nov 2018 11:51:21 +0100 Message-Id: <20181126105053.874501054@linuxfoundation.org> X-Mailer: git-send-email 2.19.2 In-Reply-To: <20181126105050.592727680@linuxfoundation.org> References: <20181126105050.592727680@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ commit fef912bf860e upstream. commit 98af4d4df889 upstream. I got a report from Howard Chen that he saw zram and sysfs race(ie, zram block device file is created but sysfs for it isn't yet) when he tried to create new zram devices via hotadd knob. v4.20 kernel fixes it by [1, 2] but it's too large size to merge into -stable so this patch fixes the problem by registering defualt group by Greg KH's approach[3]. This patch should be applied to every stable tree [3.16+] currently existing from kernel.org because the problem was introduced at 2.6.37 by [4]. [1] fef912bf860e, block: genhd: add 'groups' argument to device_add_disk [2] 98af4d4df889, zram: register default groups with device_add_disk() [3] http://kroah.com/log/blog/2013/06/26/how-to-create-a-sysfs-file-correctly/ [4] 33863c21e69e9, Staging: zram: Replace ioctls with sysfs interface Cc: Sergey Senozhatsky Cc: Hannes Reinecke Tested-by: Howard Chen Signed-off-by: Minchan Kim Signed-off-by: Sasha Levin --- drivers/block/zram/zram_drv.c | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-) diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c index 1e2648e4c286..27b202c64c84 100644 --- a/drivers/block/zram/zram_drv.c +++ b/drivers/block/zram/zram_drv.c @@ -1491,6 +1491,11 @@ static const struct attribute_group zram_disk_attr_group = { .attrs = zram_disk_attrs, }; +static const struct attribute_group *zram_disk_attr_groups[] = { + &zram_disk_attr_group, + NULL, +}; + /* * Allocate and initialize new zram device. the function returns * '>= 0' device_id upon success, and negative value otherwise. @@ -1568,23 +1573,14 @@ static int zram_add(void) if (ZRAM_LOGICAL_BLOCK_SIZE == PAGE_SIZE) blk_queue_max_write_zeroes_sectors(zram->disk->queue, UINT_MAX); + disk_to_dev(zram->disk)->groups = zram_disk_attr_groups; add_disk(zram->disk); - ret = sysfs_create_group(&disk_to_dev(zram->disk)->kobj, - &zram_disk_attr_group); - if (ret < 0) { - pr_err("Error creating sysfs group for device %d\n", - device_id); - goto out_free_disk; - } strlcpy(zram->compressor, default_compressor, sizeof(zram->compressor)); pr_info("Added device: %s\n", zram->disk->disk_name); return device_id; -out_free_disk: - del_gendisk(zram->disk); - put_disk(zram->disk); out_free_queue: blk_cleanup_queue(queue); out_free_idr: @@ -1612,16 +1608,6 @@ static int zram_remove(struct zram *zram) zram->claim = true; mutex_unlock(&bdev->bd_mutex); - /* - * Remove sysfs first, so no one will perform a disksize - * store while we destroy the devices. This also helps during - * hot_remove -- zram_reset_device() is the last holder of - * ->init_lock, no later/concurrent disksize_store() or any - * other sysfs handlers are possible. - */ - sysfs_remove_group(&disk_to_dev(zram->disk)->kobj, - &zram_disk_attr_group); - /* Make sure all the pending I/O are finished */ fsync_bdev(bdev); zram_reset_device(zram); -- 2.17.1