Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jan Kara <jack@suse.cz>
Cc: stable@vger.kernel.org, linux-block@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>,
	Logan Gunthorpe <logang@deltatee.com>,
	Donald Buczek <buczek@molgen.mpg.de>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: fix bio_clone_blkg_association() to associate with proper blkcg_gq
Date: Wed, 8 Jun 2022 14:06:43 +0200	[thread overview]
Message-ID: <YqCQ0xJBpAqbbF/k@kroah.com> (raw)
In-Reply-To: <20220608114528.15611-1-jack@suse.cz>

On Wed, Jun 08, 2022 at 01:45:28PM +0200, Jan Kara wrote:
> commit 22b106e5355d6e7a9c3b5cb5ed4ef22ae585ea94 upstream.
> 
> Commit d92c370a16cb ("block: really clone the block cgroup in
> bio_clone_blkg_association") changed bio_clone_blkg_association() to
> just clone bio->bi_blkg reference from source to destination bio. This
> is however wrong if the source and destination bios are against
> different block devices because struct blkcg_gq is different for each
> bdev-blkcg pair. This will result in IOs being accounted (and throttled
> as a result) multiple times against the same device (src bdev) while
> throttling of the other device (dst bdev) is ignored. In case of BFQ the
> inconsistency can even result in crashes in bfq_bic_update_cgroup().
> Fix the problem by looking up correct blkcg_gq for the cloned bio.
> 
> Reported-by: Logan Gunthorpe <logang@deltatee.com>
> Reported-and-tested-by: Donald Buczek <buczek@molgen.mpg.de>
> Fixes: d92c370a16cb ("block: really clone the block cgroup in bio_clone_blkg_association")
> CC: stable@vger.kernel.org
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Jan Kara <jack@suse.cz>
> Link: https://lore.kernel.org/r/20220602081242.7731-1-jack@suse.cz
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> ---
>  block/blk-cgroup.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> This patch should be a backport for 5.15, 5.17, and 5.18 stable branches.

Now queued up, thanks.

greg k-h

  reply	other threads:[~2022-06-08 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 11:45 [PATCH] block: fix bio_clone_blkg_association() to associate with proper blkcg_gq Jan Kara
2022-06-08 12:06 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-01 16:34 Jan Kara
2022-06-01 17:42 ` Christoph Hellwig
2022-06-02  7:30   ` Jan Kara
2022-06-01 19:58 ` Donald Buczek

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=YqCQ0xJBpAqbbF/k@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=buczek@molgen.mpg.de \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=logang@deltatee.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