From: Sasha Levin <sashal@kernel.org>
To: Minchan Kim <minchan@kernel.org>
Cc: stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
hare@suse.com, LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Howard Chen <howardsoc@google.com>
Subject: Re: [PATCH for v4.14] zram: close udev startup race condition as default groups
Date: Fri, 23 Nov 2018 13:50:55 -0500 [thread overview]
Message-ID: <20181123185055.GD1917@sasha-vm> (raw)
In-Reply-To: <20181123062550.163536-1-minchan@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 <sergey.senozhatsky@gmail.com>
>Cc: Hannes Reinecke <hare@suse.com>
>Tested-by: Howard Chen <howardsoc@google.com>
>Signed-off-by: Minchan Kim <minchan@kernel.org>
I've queued all 4 to their respective branches, thank you.
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-23 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 5:52 [PATCH] zram: close udev startup race condition as default groups Minchan Kim
2018-11-14 7:09 ` Hannes Reinecke
2018-11-15 17:45 ` Sasha Levin
2018-11-16 15:48 ` Minchan Kim
2018-11-23 6:25 ` [PATCH for v4.14] " Minchan Kim
2018-11-23 18:50 ` Sasha Levin [this message]
2018-11-23 6:28 ` [PATCH for 4.9] " Minchan Kim
2018-11-23 6:30 ` [PATCH] [PATCH for v4.4] " Minchan Kim
2018-11-23 6:30 ` [PATCH] [PATCH for v3.18] " Minchan Kim
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=20181123185055.GD1917@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hare@suse.com \
--cc=howardsoc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).