[GIT PULL] md-6.17-20250909

[GIT PULL] md-6.17-20250909

[Yu Kuai]

Hi, Jens

Please consider pulling following changes on your for-6.18/block branch,
this pull request contains:

 - add kconfig for internal bitmap;
 - introduce new experimental feature lockless bitmap;

Thanks,
Kuai

The following changes since commit ba28afbd9eff2a6370f23ef4e6a036ab0cfda409:

  blk-mq: fix blk_mq_tags double free while nr_requests grown (2025-09-05 13:52:52 -0600)

are available in the Git repository at:

  https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909

for you to fetch changes up to 5ab829f1971dc99f2aac10846c378e67fc875abc:

  md/md-llbitmap: introduce new lockless bitmap (2025-09-06 17:27:51 +0800)

----------------------------------------------------------------
Yu Kuai (24):
      md/md-bitmap: remove the parameter 'init' for bitmap_ops->resize()
      md/md-bitmap: merge md_bitmap_group into bitmap_operations
      md/md-bitmap: add a new parameter 'flush' to bitmap_ops->enabled
      md/md-bitmap: add md_bitmap_registered/enabled() helper
      md/md-bitmap: handle the case bitmap is not enabled before start_sync()
      md/md-bitmap: handle the case bitmap is not enabled before end_sync()
      md/raid1: check bitmap before behind write
      md/raid1: check before referencing mddev->bitmap_ops
      md/raid10: check before referencing mddev->bitmap_ops
      md/raid5: check before referencing mddev->bitmap_ops
      md/dm-raid: check before referencing mddev->bitmap_ops
      md: check before referencing mddev->bitmap_ops
      md/md-bitmap: introduce CONFIG_MD_BITMAP
      md: add a new parameter 'offset' to md_super_write()
      md: factor out a helper raid_is_456()
      md/md-bitmap: support discard for bitmap ops
      md: add a new mddev field 'bitmap_id'
      md/md-bitmap: add a new sysfs api bitmap_type
      md/md-bitmap: delay registration of bitmap_ops until creating bitmap
      md/md-bitmap: add a new method skip_sync_blocks() in bitmap_operations
      md/md-bitmap: add a new method blocks_synced() in bitmap_operations
      md: add a new recovery_flag MD_RECOVERY_LAZY_RECOVER
      md/md-bitmap: make method bitmap_ops->daemon_work optional
      md/md-llbitmap: introduce new lockless bitmap

 Documentation/admin-guide/md.rst |   86 +++++---
 drivers/md/Kconfig               |   29 +++
 drivers/md/Makefile              |    4 +-
 drivers/md/dm-raid.c             |   18 +-
 drivers/md/md-bitmap.c           |   89 ++++----
 drivers/md/md-bitmap.h           |  107 +++++++++-
 drivers/md/md-cluster.c          |    2 +-
 drivers/md/md-llbitmap.c         | 1626 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/md/md.c                  |  378 +++++++++++++++++++++++++++-------
 drivers/md/md.h                  |   24 ++-
 drivers/md/raid1-10.c            |    2 +-
 drivers/md/raid1.c               |   79 ++++---
 drivers/md/raid10.c              |   49 ++---
 drivers/md/raid5.c               |   64 ++++--
 14 files changed, 2313 insertions(+), 244 deletions(-)
 create mode 100644 drivers/md/md-llbitmap.c

Re: [GIT PULL] md-6.17-20250909

[Yu Kuai]

Hi, Jens

在 2025/09/09 16:20, Yu Kuai 写道:
> Hi, Jens
> 
> Please consider pulling following changes on your for-6.18/block branch,
> this pull request contains:
> 
>   - add kconfig for internal bitmap;
>   - introduce new experimental feature lockless bitmap;
> 
> Thanks,
> Kuai
> 

Please ignore the typo in tittle, it's md-6.18-20250909 :)

Thanks,
Kuai

> The following changes since commit ba28afbd9eff2a6370f23ef4e6a036ab0cfda409:
> 
>    blk-mq: fix blk_mq_tags double free while nr_requests grown (2025-09-05 13:52:52 -0600)
> 
> are available in the Git repository at:
> 
>    https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
> 
> for you to fetch changes up to 5ab829f1971dc99f2aac10846c378e67fc875abc:
> 
>    md/md-llbitmap: introduce new lockless bitmap (2025-09-06 17:27:51 +0800)
> 
> ----------------------------------------------------------------
> Yu Kuai (24):
>        md/md-bitmap: remove the parameter 'init' for bitmap_ops->resize()
>        md/md-bitmap: merge md_bitmap_group into bitmap_operations
>        md/md-bitmap: add a new parameter 'flush' to bitmap_ops->enabled
>        md/md-bitmap: add md_bitmap_registered/enabled() helper
>        md/md-bitmap: handle the case bitmap is not enabled before start_sync()
>        md/md-bitmap: handle the case bitmap is not enabled before end_sync()
>        md/raid1: check bitmap before behind write
>        md/raid1: check before referencing mddev->bitmap_ops
>        md/raid10: check before referencing mddev->bitmap_ops
>        md/raid5: check before referencing mddev->bitmap_ops
>        md/dm-raid: check before referencing mddev->bitmap_ops
>        md: check before referencing mddev->bitmap_ops
>        md/md-bitmap: introduce CONFIG_MD_BITMAP
>        md: add a new parameter 'offset' to md_super_write()
>        md: factor out a helper raid_is_456()
>        md/md-bitmap: support discard for bitmap ops
>        md: add a new mddev field 'bitmap_id'
>        md/md-bitmap: add a new sysfs api bitmap_type
>        md/md-bitmap: delay registration of bitmap_ops until creating bitmap
>        md/md-bitmap: add a new method skip_sync_blocks() in bitmap_operations
>        md/md-bitmap: add a new method blocks_synced() in bitmap_operations
>        md: add a new recovery_flag MD_RECOVERY_LAZY_RECOVER
>        md/md-bitmap: make method bitmap_ops->daemon_work optional
>        md/md-llbitmap: introduce new lockless bitmap
> 
>   Documentation/admin-guide/md.rst |   86 +++++---
>   drivers/md/Kconfig               |   29 +++
>   drivers/md/Makefile              |    4 +-
>   drivers/md/dm-raid.c             |   18 +-
>   drivers/md/md-bitmap.c           |   89 ++++----
>   drivers/md/md-bitmap.h           |  107 +++++++++-
>   drivers/md/md-cluster.c          |    2 +-
>   drivers/md/md-llbitmap.c         | 1626 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   drivers/md/md.c                  |  378 +++++++++++++++++++++++++++-------
>   drivers/md/md.h                  |   24 ++-
>   drivers/md/raid1-10.c            |    2 +-
>   drivers/md/raid1.c               |   79 ++++---
>   drivers/md/raid10.c              |   49 ++---
>   drivers/md/raid5.c               |   64 ++++--
>   14 files changed, 2313 insertions(+), 244 deletions(-)
>   create mode 100644 drivers/md/md-llbitmap.c
> 
> .
> 

Re: [GIT PULL] md-6.17-20250909

[Jens Axboe]

On 9/9/25 2:20 AM, Yu Kuai wrote:
> Hi, Jens
> 
> Please consider pulling following changes on your for-6.18/block branch,
> this pull request contains:
> 
>  - add kconfig for internal bitmap;
>  - introduce new experimental feature lockless bitmap;

Can you write a bit of a better pull request letter? It'd be nice to get
an actual description of what the "lockless bitmap" is, and why it makes
sense to have it. This is pretty sparse...

>   https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
> 

and this is a new source for you, is the above tag signed?

-- 
Jens Axboe

Re: [GIT PULL] md-6.17-20250909

[Yu Kuai]

Hi,

在 2025/9/9 21:26, Jens Axboe 写道:
> On 9/9/25 2:20 AM, Yu Kuai wrote:
>> Hi, Jens
>>
>> Please consider pulling following changes on your for-6.18/block branch,
>> this pull request contains:
>>
>>   - add kconfig for internal bitmap;
>>   - introduce new experimental feature lockless bitmap;
> Can you write a bit of a better pull request letter? It'd be nice to get
> an actual description of what the "lockless bitmap" is, and why it makes
> sense to have it. This is pretty sparse...

Of course, details in be found in the patch 0 of the thread. I'll send a v2.

>
>>    https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
>>
> and this is a new source for you, is the above tag signed?

I thought they are the same, I'll switch back in v2.

Thanks,
Kuai

Re: [GIT PULL] md-6.17-20250909

[Jens Axboe]

On 9/9/25 10:44 AM, Yu Kuai wrote:
> Hi,
> 
> ? 2025/9/9 21:26, Jens Axboe ??:
>> On 9/9/25 2:20 AM, Yu Kuai wrote:
>>> Hi, Jens
>>>
>>> Please consider pulling following changes on your for-6.18/block branch,
>>> this pull request contains:
>>>
>>>   - add kconfig for internal bitmap;
>>>   - introduce new experimental feature lockless bitmap;
>> Can you write a bit of a better pull request letter? It'd be nice to get
>> an actual description of what the "lockless bitmap" is, and why it makes
>> sense to have it. This is pretty sparse...
> 
> Of course, details in be found in the patch 0 of the thread. I'll send a v2.

Please always write a decent message on why any pull request needs
merging.

>>>    https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
>>>
>> and this is a new source for you, is the above tag signed?
> 
> I thought they are the same, I'll switch back in v2.

They are very much NOT the same. One is some random site, the other is
the official kernel infrastructure. If you don't use git.kernel.org,
I'm definitely not pulling anything that isn't signed by a key, and
that key in turn has been signed by other people I know.

-- 
Jens Axboe

Re: [GIT PULL] md-6.17-20250909

[Jens Axboe]

On 9/9/25 10:51 AM, Jens Axboe wrote:
> On 9/9/25 10:44 AM, Yu Kuai wrote:
>> Hi,
>>
>> ? 2025/9/9 21:26, Jens Axboe ??:
>>> On 9/9/25 2:20 AM, Yu Kuai wrote:
>>>> Hi, Jens
>>>>
>>>> Please consider pulling following changes on your for-6.18/block branch,
>>>> this pull request contains:
>>>>
>>>>   - add kconfig for internal bitmap;
>>>>   - introduce new experimental feature lockless bitmap;
>>> Can you write a bit of a better pull request letter? It'd be nice to get
>>> an actual description of what the "lockless bitmap" is, and why it makes
>>> sense to have it. This is pretty sparse...
>>
>> Of course, details in be found in the patch 0 of the thread. I'll send a v2.
> 
> Please always write a decent message on why any pull request needs
> merging.
> 
>>>>    https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
>>>>
>>> and this is a new source for you, is the above tag signed?
>>
>> I thought they are the same, I'll switch back in v2.
> 
> They are very much NOT the same. One is some random site, the other is
> the official kernel infrastructure. If you don't use git.kernel.org,
> I'm definitely not pulling anything that isn't signed by a key, and
> that key in turn has been signed by other people I know.

Oh and since I keep getting these, the last 5 pull requests you have
sent me have CC'ed:

inux-raid@vger.kernel.org

which of course doesn't exist, and hence the md list doesn't get
your PR emails, and I get failure notifications when I reply.
I'm assuming this is in your scripts somewhere, and I keep
thinking "it was a typo, hence a one time thing", but no, it keeps
being there every time. Can you please fix your script to use the
actually correct email?

-- 
Jens Axboe

Re: [GIT PULL] md-6.17-20250909

[Yu Kuai]

Hi,

在 2025/9/10 0:54, Jens Axboe 写道:
> On 9/9/25 10:51 AM, Jens Axboe wrote:
>> On 9/9/25 10:44 AM, Yu Kuai wrote:
>>> Hi,
>>>
>>> ? 2025/9/9 21:26, Jens Axboe ??:
>>>> On 9/9/25 2:20 AM, Yu Kuai wrote:
>>>>> Hi, Jens
>>>>>
>>>>> Please consider pulling following changes on your for-6.18/block branch,
>>>>> this pull request contains:
>>>>>
>>>>>    - add kconfig for internal bitmap;
>>>>>    - introduce new experimental feature lockless bitmap;
>>>> Can you write a bit of a better pull request letter? It'd be nice to get
>>>> an actual description of what the "lockless bitmap" is, and why it makes
>>>> sense to have it. This is pretty sparse...
>>> Of course, details in be found in the patch 0 of the thread. I'll send a v2.
>> Please always write a decent message on why any pull request needs
>> merging.
>>
>>>>>     https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
>>>>>
>>>> and this is a new source for you, is the above tag signed?
>>> I thought they are the same, I'll switch back in v2.
>> They are very much NOT the same. One is some random site, the other is
>> the official kernel infrastructure. If you don't use git.kernel.org,
>> I'm definitely not pulling anything that isn't signed by a key, and
>> that key in turn has been signed by other people I know.
> Oh and since I keep getting these, the last 5 pull requests you have
> sent me have CC'ed:
>
> inux-raid@vger.kernel.org
>
> which of course doesn't exist, and hence the md list doesn't get
> your PR emails, and I get failure notifications when I reply.
> I'm assuming this is in your scripts somewhere, and I keep
> thinking "it was a typo, hence a one time thing", but no, it keeps
> being there every time. Can you please fix your script to use the
> actually correct email?

Of course, lessons are learned. Sorry for the typo, I just checked and
I do get the failure notifications as well.

Thanks!
Kuai