Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: chengzhihao1@huawei.com, Stable@vger.kernel.org, richard@nod.at,
	yi.zhang@huawei.com
Subject: Re: FAILED: patch "[PATCH] ubifs: Fix deadlock in concurrent bulk-read and writepage" failed to apply to 4.9-stable tree
Date: Thu, 6 Feb 2020 20:21:40 -0500	[thread overview]
Message-ID: <20200207012140.GS31482@sasha-vm> (raw)
In-Reply-To: <1581016848106213@kroah.com>

On Thu, Feb 06, 2020 at 08:20:48PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From f5de5b83303e61b1f3fb09bd77ce3ac2d7a475f2 Mon Sep 17 00:00:00 2001
>From: Zhihao Cheng <chengzhihao1@huawei.com>
>Date: Sat, 11 Jan 2020 17:50:36 +0800
>Subject: [PATCH] ubifs: Fix deadlock in concurrent bulk-read and writepage
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>In ubifs, concurrent execution of writepage and bulk read on the same file
>may cause ABBA deadlock, for example (Reproduce method see Link):
>
>Process A(Bulk-read starts from page4)         Process B(write page4 back)
>  vfs_read                                       wb_workfn or fsync
>  ...                                            ...
>  generic_file_buffered_read                     write_cache_pages
>    ubifs_readpage                                 LOCK(page4)
>
>      ubifs_bulk_read                              ubifs_writepage
>        LOCK(ui->ui_mutex)                           ubifs_write_inode
>
>	  ubifs_do_bulk_read                           LOCK(ui->ui_mutex)
>	    find_or_create_page(alloc page4)                  ↑
>	      LOCK(page4)                   <--     ABBA deadlock occurs!
>
>In order to ensure the serialization execution of bulk read, we can't
>remove the big lock 'ui->ui_mutex' in ubifs_bulk_read(). Instead, we
>allow ubifs_do_bulk_read() to lock page failed by replacing
>find_or_create_page(FGP_LOCK) with
>pagecache_get_page(FGP_LOCK | FGP_NOWAIT).
>
>Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
>Suggested-by: zhangyi (F) <yi.zhang@huawei.com>
>Cc: <Stable@vger.kernel.org>
>Fixes: 4793e7c5e1c ("UBIFS: add bulk-read facility")
>Link: https://bugzilla.kernel.org/show_bug.cgi?id=206153
>Signed-off-by: Richard Weinberger <richard@nod.at>

I took in 480a1a6a3ef6 ("ubifs: Change gfp flags in page allocation for
bulk read") as dependency and queued both for 4.9 and 4.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2020-02-07  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 19:20 FAILED: patch "[PATCH] ubifs: Fix deadlock in concurrent bulk-read and writepage" failed to apply to 4.9-stable tree gregkh
2020-02-07  1:21 ` Sasha Levin [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=20200207012140.GS31482@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Stable@vger.kernel.org \
    --cc=chengzhihao1@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=richard@nod.at \
    --cc=yi.zhang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox