From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Hyeoncheol Lee <cheol.lee@lge.com>,
yjay.kim@lge.com, Sangseok Lee <sangseok.lee@lge.com>,
Hugh Dickins <hughd@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3 3/3] zram: support BDI_CAP_STABLE_WRITES
Date: Sun, 27 Nov 2016 22:01:04 +0900 [thread overview]
Message-ID: <20161127130104.GA4919@tigerII> (raw)
In-Reply-To: <20161126144104.GA2189@blaptop>
On (11/26/16 23:41), Minchan Kim wrote:
[..]
> > > mutex_lock(&bdev->bd_mutex);
> >
> > why not set it just once, when we allocate queue/disk and configure both
> > of them: in zram_add()
>
> I should have mentioned the reason.
> The revalidate_disk reset the BDI_CAP_STABLE_WRITES.
aha. either sets or clears it in blk_integrity_revalidate(),
now I see it.
-ss
prev parent reply other threads:[~2016-11-27 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 8:35 [PATCH v3 0/3] Fix zsmalloc crash problem Minchan Kim
2016-11-25 8:35 ` [PATCH v3 1/3] mm: support anonymous stable page Minchan Kim
2016-11-25 8:35 ` Minchan Kim
2016-11-27 13:19 ` Sergey Senozhatsky
2016-11-27 13:19 ` Sergey Senozhatsky
2016-11-28 0:41 ` Minchan Kim
2016-11-28 0:41 ` Minchan Kim
2016-11-28 5:38 ` Sergey Senozhatsky
2016-11-28 5:38 ` Sergey Senozhatsky
2016-11-25 8:35 ` [PATCH v3 2/3] zram: revalidate disk under init_lock Minchan Kim
2016-11-26 6:38 ` Sergey Senozhatsky
2016-11-25 8:35 ` [PATCH v3 3/3] zram: support BDI_CAP_STABLE_WRITES Minchan Kim
2016-11-26 6:37 ` Sergey Senozhatsky
2016-11-26 14:41 ` Minchan Kim
2016-11-27 13:01 ` Sergey Senozhatsky [this message]
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=20161127130104.GA4919@tigerII \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cheol.lee@lge.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=sangseok.lee@lge.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=yjay.kim@lge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.