Message ID | ECA01A7B-4737-45A7-B853-2A41069173F7@fb.com (mailing list archive) |
---|---|
State | Accepted, archived |
Headers | show |
Series | [GIT,PULL] md-fixes 20230315 | expand |
On 3/15/23 12:04 PM, Song Liu wrote: > Hi Jens, > > Please consider pulling the following fixes on top of your for-6.3/block > branch. This set contains two fixes for old issues (by Neil) and one fix > for 6.3 (by Xiao). > > Thanks, > Song > > > The following changes since commit 49d24398327e32265eccdeec4baeb5a6a609c0bd: > > blk-mq: enforce op-specific segment limits in blk_insert_cloned_request (2023-03-02 21:00:20 -0700) > > are available in the Git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes > > for you to fetch changes up to f6bb5176318186880ff2f16ad65f519b70f04686: > > Subject: md: select BLOCK_LEGACY_AUTOLOAD (2023-03-13 13:34:29 -0700) > > ---------------------------------------------------------------- > NeilBrown (2): > md: avoid signed overflow in slot_store() > Subject: md: select BLOCK_LEGACY_AUTOLOAD This one looks like it got botched when applying?
> On Mar 15, 2023, at 11:09 AM, Jens Axboe <axboe@kernel.dk> wrote: > > On 3/15/23 12:04 PM, Song Liu wrote: >> Hi Jens, >> >> Please consider pulling the following fixes on top of your for-6.3/block >> branch. This set contains two fixes for old issues (by Neil) and one fix >> for 6.3 (by Xiao). >> >> Thanks, >> Song >> >> >> The following changes since commit 49d24398327e32265eccdeec4baeb5a6a609c0bd: >> >> blk-mq: enforce op-specific segment limits in blk_insert_cloned_request (2023-03-02 21:00:20 -0700) >> >> are available in the Git repository at: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes >> >> for you to fetch changes up to f6bb5176318186880ff2f16ad65f519b70f04686: >> >> Subject: md: select BLOCK_LEGACY_AUTOLOAD (2023-03-13 13:34:29 -0700) >> >> ---------------------------------------------------------------- >> NeilBrown (2): >> md: avoid signed overflow in slot_store() >> Subject: md: select BLOCK_LEGACY_AUTOLOAD > > This one looks like it got botched when applying? Yeah, I messed up the subject. Thanks for catching it. I just fixed the subject. Please pull the following instead. Sorry for the problem. Song The following changes since commit 49d24398327e32265eccdeec4baeb5a6a609c0bd: blk-mq: enforce op-specific segment limits in blk_insert_cloned_request (2023-03-02 21:00:20 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes for you to fetch changes up to 6c0f5898836c05c6d850a750ed7940ba29e4e6c5: md: select BLOCK_LEGACY_AUTOLOAD (2023-03-15 11:12:14 -0700) ---------------------------------------------------------------- NeilBrown (2): md: avoid signed overflow in slot_store() md: select BLOCK_LEGACY_AUTOLOAD Xiao Ni (1): md: Free resources in __md_stop drivers/md/Kconfig | 4 ++++ drivers/md/md.c | 17 ++++++++--------- 2 files changed, 12 insertions(+), 9 deletions(-)
On 3/15/23 12:14?PM, Song Liu wrote: > > >> On Mar 15, 2023, at 11:09 AM, Jens Axboe <axboe@kernel.dk> wrote: >> >> On 3/15/23 12:04?PM, Song Liu wrote: >>> Hi Jens, >>> >>> Please consider pulling the following fixes on top of your for-6.3/block >>> branch. This set contains two fixes for old issues (by Neil) and one fix >>> for 6.3 (by Xiao). >>> >>> Thanks, >>> Song >>> >>> >>> The following changes since commit 49d24398327e32265eccdeec4baeb5a6a609c0bd: >>> >>> blk-mq: enforce op-specific segment limits in blk_insert_cloned_request (2023-03-02 21:00:20 -0700) >>> >>> are available in the Git repository at: >>> >>> https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-fixes >>> >>> for you to fetch changes up to f6bb5176318186880ff2f16ad65f519b70f04686: >>> >>> Subject: md: select BLOCK_LEGACY_AUTOLOAD (2023-03-13 13:34:29 -0700) >>> >>> ---------------------------------------------------------------- >>> NeilBrown (2): >>> md: avoid signed overflow in slot_store() >>> Subject: md: select BLOCK_LEGACY_AUTOLOAD >> >> This one looks like it got botched when applying? > > Yeah, I messed up the subject. Thanks for catching it. I just fixed the > subject. Please pull the following instead. Pulled.