mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Yu Kuai <yukuai@fnnas.com>,
	linux-block@vger.kernel.org, linux-raid@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, heinzm@redhat.com,
	jiashengjiangcool@gmail.com, jinpu.wang@ionos.com,
	linan122@huawei.com
Subject: Re: [GIT PULL] md-7.0-20260127
Date: Mon, 26 Jan 2026 21:09:51 -0700	[thread overview]
Message-ID: <8a6842a5-864d-4bde-9a9b-1af9368b1a5f@kernel.dk> (raw)
In-Reply-To: <20260126172008.343807-1-yukuai@fnnas.com>

On 1/26/26 10:20 AM, Yu Kuai wrote:
> Hi Jens,
> 
> Please consider pulling the following changes into your for-7.0/block
> branch.
> 
> This pull request contains:
> 
> Bug Fixes:
> - Fix raid5_run() to return error when log_init() fails (Yu Kuai)
> - Fix IO hang with degraded array with llbitmap (Yu Kuai)
> - Fix percpu_ref not resurrected on suspend timeout in llbitmap (Yu Kuai)
> - Fix GPF in write_page caused by resize race (Jack Wang)
> - Fix NULL pointer dereference in process_metadata_update (Jiasheng Jiang)
> - Fix hang when stopping arrays with metadata through dm-raid
>   (Heinz Mauelshagen)
> - Fix any_working flag handling in raid10_sync_request (Li Nan)
> 
> Cleanups & Refactoring:
> - Refactor sync/recovery code path, improve error handling for badblocks,
>   and remove unused recovery_disabled field (Li Nan)
> - Consolidate mddev boolean fields into mddev_flags (Yu Kuai)
> 
> Improvements:
> - Use mempool to allocate stripe_request_ctx and make sure max_sectors is
>   not less than io_opt in raid5 (Yu Kuai)

Pulled, thanks.

-- 
Jens Axboe


      reply	other threads:[~2026-01-27  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 17:20 Yu Kuai
2026-01-27  4:09 ` Jens Axboe [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=8a6842a5-864d-4bde-9a9b-1af9368b1a5f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=heinzm@redhat.com \
    --cc=jiashengjiangcool@gmail.com \
    --cc=jinpu.wang@ionos.com \
    --cc=linan122@huawei.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=yukuai@fnnas.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

all inboxes | Powered by JetHome®