From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 551C4C43441 for ; Fri, 23 Nov 2018 18:51:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0D55C20863 for ; Fri, 23 Nov 2018 18:51:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="i7RA/Gly" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0D55C20863 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437305AbeKXFg1 (ORCPT ); Sat, 24 Nov 2018 00:36:27 -0500 Received: from mail.kernel.org ([198.145.29.99]:59224 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731652AbeKXFg1 (ORCPT ); Sat, 24 Nov 2018 00:36:27 -0500 Received: from localhost (unknown [37.142.5.207]) (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 0B0D120824; Fri, 23 Nov 2018 18:50:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1542999058; bh=zK2HkS4s+a6ZVzV0MneNGWByuSYoihWQ1ldO2vE91fQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=i7RA/Glyx0HJBfH0NDmZmghYw8/UJyf3KrluWWY5cJxVPhJkI9IG5ugcpDzLOo79E S8+vQUogn+k8gyFc2MBU/RZiFQ1aW0wL1lpy5LASF4ZJnsPYJwoZbX4N8KVHPgGwoV 5h7ekIdIDBOkosEJzDnVoGZUNtICdk82tgJyxILs= Date: Fri, 23 Nov 2018 13:50:55 -0500 From: Sasha Levin To: Minchan Kim Cc: stable@vger.kernel.org, Andrew Morton , hare@suse.com, LKML , Sergey Senozhatsky , Howard Chen Subject: Re: [PATCH for v4.14] zram: close udev startup race condition as default groups Message-ID: <20181123185055.GD1917@sasha-vm> References: <20181115174504.GJ95254@sasha-vm> <20181123062550.163536-1-minchan@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20181123062550.163536-1-minchan@kernel.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 23, 2018 at 03:25:50PM +0900, Minchan Kim wrote: >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 I've queued all 4 to their respective branches, thank you. -- Thanks, Sasha