[PATCH] scsi: zorro7xx: put SCSI host on remove

[PATCH] scsi: zorro7xx: put SCSI host on remove

[Guangshuo Li]

zorro7xx_init_one() obtains a SCSI host through NCR_700_detect(). The
probe failure path drops the host reference with scsi_host_put(), but
the normal remove path does not perform the corresponding cleanup.

As a result, the SCSI host reference remains allocated after the
device is removed.

Call scsi_host_put() after all users of the SCSI host have been torn
down to release the reference acquired during probe.

This issue was found by manual code inspection.

Fixes: 45804fbb00ee ("[SCSI] 53c700: Amiga Zorro NCR53c710 SCSI")
Cc: stable@vger.kernel.org
Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
---
 drivers/scsi/zorro7xx.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/scsi/zorro7xx.c b/drivers/scsi/zorro7xx.c
index 21c769dc1ecb..a8b0c2d4a9cb 100644
--- a/drivers/scsi/zorro7xx.c
+++ b/drivers/scsi/zorro7xx.c
@@ -164,6 +164,7 @@ static void zorro7xx_remove_one(struct zorro_dev *z)
 	kfree(hostdata);
 	free_irq(host->irq, host);
 	zorro_release_device(z);
+	scsi_host_put(host);
 }
 
 static struct zorro_driver zorro7xx_driver = {
-- 
2.43.0

Re: [PATCH] scsi: zorro7xx: put SCSI host on remove

[krzk]

On Sat, 19 Sep 2026 02:02:01 +0800, Guangshuo Li wrote:
> zorro7xx_init_one() obtains a SCSI host through NCR_700_detect(). The
> probe failure path drops the host reference with scsi_host_put(), but
> the normal remove path does not perform the corresponding cleanup.
> 
> As a result, the SCSI host reference remains allocated after the
> device is removed.
> 
> Call scsi_host_put() after all users of the SCSI host have been torn
> down to release the reference acquired during probe.
> 
> This issue was found by manual code inspection.
> 
> Fixes: 45804fbb00ee ("[SCSI] 53c700: Amiga Zorro NCR53c710 SCSI")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
>  drivers/scsi/zorro7xx.c | 1 +
>  1 file changed, 1 insertion(+)
> 


You sent multiple independent patches, to multiple independent
subsystems. The amount of these patches clearly suggest this was
AI generated and most likely not tested.

More importantly, you sent all this work without properly organizing
relevant patches into patchsets. This makes reviewing difficult
and might cause multiple reviewers to address the same issue.
Replying to the entire set is impossible and requires handling each
patch independently, instead of applying or discarding the set.
Maintainers also won't see the bigger picture of your work. Quite
worrying.

This is on the verge of hostile patch: bomb us with so many
contributions, we won't be able to handle them in efficient manner,
like responding ONCE to ask you to slow down.  Considering all this
is untested and LLM generated, I have even more doubts whether this
should be considered for review.

Please read kernel documentation BEFORE posting more work. It will
explain you how to identify subsystems, how to organize your work per
subsystem, how to document usage of LLM and how what you should not
do if this was posted in a good faith.

Best regards,
Krzysztof

Re: [PATCH] scsi: zorro7xx: put SCSI host on remove

[Guangshuo Li]

Hi Krzysztof,

Thank you for your feedback.

On Mon, 21 Sept 2026 at 23:17, <krzk@kernel.org> wrote:
>
>
> On Sat, 19 Sep 2026 02:02:01 +0800, Guangshuo Li wrote:
> > zorro7xx_init_one() obtains a SCSI host through NCR_700_detect(). The
> > probe failure path drops the host reference with scsi_host_put(), but
> > the normal remove path does not perform the corresponding cleanup.
> >
> > As a result, the SCSI host reference remains allocated after the
> > device is removed.
> >
> > Call scsi_host_put() after all users of the SCSI host have been torn
> > down to release the reference acquired during probe.
> >
> > This issue was found by manual code inspection.
> >
> > Fixes: 45804fbb00ee ("[SCSI] 53c700: Amiga Zorro NCR53c710 SCSI")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> > ---
> >  drivers/scsi/zorro7xx.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
>
>
> You sent multiple independent patches, to multiple independent
> subsystems. The amount of these patches clearly suggest this was
> AI generated and most likely not tested.
>
> More importantly, you sent all this work without properly organizing
> relevant patches into patchsets. This makes reviewing difficult
> and might cause multiple reviewers to address the same issue.
> Replying to the entire set is impossible and requires handling each
> patch independently, instead of applying or discarding the set.
> Maintainers also won't see the bigger picture of your work. Quite
> worrying.
>
> This is on the verge of hostile patch: bomb us with so many
> contributions, we won't be able to handle them in efficient manner,
> like responding ONCE to ask you to slow down.  Considering all this
> is untested and LLM generated, I have even more doubts whether this
> should be considered for review.
>
> Please read kernel documentation BEFORE posting more work. It will
> explain you how to identify subsystems, how to organize your work per
> subsystem, how to document usage of LLM and how what you should not
> do if this was posted in a good faith.
>
> Best regards,
> Krzysztof
>
>
>
I would like to clarify that these patches were manually reviewed and
audited by us; they were not simply generated and submitted by an LLM.
However, I understand why the recent submission pattern may have given
that impression. We sent too many patches in a short period of time,
and we also failed to respond to some discussions in a timely manner,
which made the situation look worse.

Many of the recent patches, especially the v2 revisions, are
corrections and improvements based on previous review feedback rather
than completely new untested changes. That said, we recognize that the
way we submitted them increased the burden on maintainers and
reviewers.

We apologize for the pressure this caused to the community. We will be
more careful about organizing patches by subsystem, preparing proper
patchsets, and following the kernel contribution guidelines before
sending future work.

Thank you again for pointing this out.

Best regards,
Guangshuo