All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: tglx@linutronix.de,  Guanrui Huang <guanrui.huang@linux.alibaba.com>
Cc: yuzenghui@huawei.com, shannon.zhao@linux.alibaba.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] irqchip/gic-v3-its: Fix double free on error
Date: Thu, 18 Apr 2024 08:18:59 +0100	[thread overview]
Message-ID: <8734rjrvdo.wl-maz@kernel.org> (raw)
In-Reply-To: <20240418061053.96803-1-guanrui.huang@linux.alibaba.com>

On Thu, 18 Apr 2024 07:10:51 +0100,
Guanrui Huang <guanrui.huang@linux.alibaba.com> wrote:
> 
> Hello everyone, this is the v5 of the patch to fix double free 
> in gic driver.
> 
> The differences from the v3 and v4:
> 1. modify description: add "Fixes" in patch 1, as suggested by Markus Elfring.
> 
> 2. improve patch granularity: split 'remove BUG_ON' into a secord patch, 
>    as suggested by Zenghui and Markus Elfring.
> 
> 3. modify description: explain why the BUG_ON is useless in patch 2, 
>    as suggested by Marc Zyngier.
> 
> Thanks,
> Guanrui
> 
> Guanrui Huang (2):
>   irqchip/gic-v3-its: Fix double free on error
>   irqchip/gic-v3-its: remove BUG_ON in its_vpe_irq_domain_alloc
> 
>  drivers/irqchip/irq-gic-v3-its.c | 11 ++---------
>  1 file changed, 2 insertions(+), 9 deletions(-)
> 

Thomas, can you please take this in for 6.10?

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: tglx@linutronix.de,  Guanrui Huang <guanrui.huang@linux.alibaba.com>
Cc: yuzenghui@huawei.com, shannon.zhao@linux.alibaba.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] irqchip/gic-v3-its: Fix double free on error
Date: Thu, 18 Apr 2024 08:18:59 +0100	[thread overview]
Message-ID: <8734rjrvdo.wl-maz@kernel.org> (raw)
In-Reply-To: <20240418061053.96803-1-guanrui.huang@linux.alibaba.com>

On Thu, 18 Apr 2024 07:10:51 +0100,
Guanrui Huang <guanrui.huang@linux.alibaba.com> wrote:
> 
> Hello everyone, this is the v5 of the patch to fix double free 
> in gic driver.
> 
> The differences from the v3 and v4:
> 1. modify description: add "Fixes" in patch 1, as suggested by Markus Elfring.
> 
> 2. improve patch granularity: split 'remove BUG_ON' into a secord patch, 
>    as suggested by Zenghui and Markus Elfring.
> 
> 3. modify description: explain why the BUG_ON is useless in patch 2, 
>    as suggested by Marc Zyngier.
> 
> Thanks,
> Guanrui
> 
> Guanrui Huang (2):
>   irqchip/gic-v3-its: Fix double free on error
>   irqchip/gic-v3-its: remove BUG_ON in its_vpe_irq_domain_alloc
> 
>  drivers/irqchip/irq-gic-v3-its.c | 11 ++---------
>  1 file changed, 2 insertions(+), 9 deletions(-)
> 

Thomas, can you please take this in for 6.10?

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2024-04-18  7:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  6:10 [PATCH v5 0/2] irqchip/gic-v3-its: Fix double free on error Guanrui Huang
2024-04-18  6:10 ` Guanrui Huang
2024-04-18  6:10 ` [PATCH v5 1/2] " Guanrui Huang
2024-04-18  6:10   ` Guanrui Huang
2024-04-18  7:55   ` Markus Elfring
2024-04-18  7:55     ` Markus Elfring
2024-04-25 12:46   ` [tip: irq/urgent] irqchip/gic-v3-its: Prevent " tip-bot2 for Guanrui Huang
2024-04-18  6:10 ` [PATCH v5 2/2] irqchip/gic-v3-its: remove BUG_ON in its_vpe_irq_domain_alloc Guanrui Huang
2024-04-18  6:10   ` Guanrui Huang
2024-04-18  6:56   ` Zenghui Yu
2024-04-18  6:56     ` Zenghui Yu
2024-04-25 12:46   ` [tip: irq/core] irqchip/gic-v3-its: Remove " tip-bot2 for Guanrui Huang
2024-04-18  7:18 ` Marc Zyngier [this message]
2024-04-18  7:18   ` [PATCH v5 0/2] irqchip/gic-v3-its: Fix double free on error Marc Zyngier

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=8734rjrvdo.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=guanrui.huang@linux.alibaba.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shannon.zhao@linux.alibaba.com \
    --cc=tglx@linutronix.de \
    --cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.