All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: andreyknvl@gmail.com,
	"Qun-wei Lin (林群崴)" <Qun-wei.Lin@mediatek.com>,
	"Guangye Yang (杨光业)" <guangye.yang@mediatek.com>,
	linux-mm@kvack.org,
	"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
	kasan-dev@googlegroups.com, ryabinin.a.a@gmail.com,
	linux-arm-kernel@lists.infradead.org, vincenzo.frascino@arm.com,
	will@kernel.org, eugenis@google.com,
	"Kuan-Ying Lee (李冠穎)" <Kuan-Ying.Lee@mediatek.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] arm64: Reset KASAN tag in copy_highpage with HW tags only
Date: Wed, 15 Feb 2023 13:46:01 +0000	[thread overview]
Message-ID: <Y+ziGQAB3nhVqFY3@arm.com> (raw)
In-Reply-To: <CAMn1gO4mKL4od8_4+RH9T2C+6+-7=rsdLrSNpghsbMyoVExCjA@mail.gmail.com>

On Tue, Feb 14, 2023 at 08:44:36PM -0800, Peter Collingbourne wrote:
> On Tue, Feb 14, 2023 at 9:54 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > If yes, I think we should use:
> >
> > Fixes: 20794545c146 ("arm64: kasan: Revert "arm64: mte: reset the page tag in page->flags"")
> > Cc: <stable@vger.kernel.org> # 6.0.x
> 
> I agree with the Fixes tag, but are you sure that 6.0.y is still
> supported as a stable kernel release? kernel.org only lists 6.1, and I
> don't see any updates to Greg's linux-6.0.y branch since January 12.

Yeah, that doesn't matter. I normally generate this with a git alias and
it matches the release containing the commit. I don't have to think
about which stable kernels are still maintained.

> I'm having some email trouble at the moment so I can't send a v2, so
> please feel free to add the Fixes tag yourself.

I can add the fixes tag.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: andreyknvl@gmail.com,
	"Qun-wei Lin (林群崴)" <Qun-wei.Lin@mediatek.com>,
	"Guangye Yang (杨光业)" <guangye.yang@mediatek.com>,
	linux-mm@kvack.org,
	"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
	kasan-dev@googlegroups.com, ryabinin.a.a@gmail.com,
	linux-arm-kernel@lists.infradead.org, vincenzo.frascino@arm.com,
	will@kernel.org, eugenis@google.com,
	"Kuan-Ying Lee (李冠穎)" <Kuan-Ying.Lee@mediatek.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] arm64: Reset KASAN tag in copy_highpage with HW tags only
Date: Wed, 15 Feb 2023 13:46:01 +0000	[thread overview]
Message-ID: <Y+ziGQAB3nhVqFY3@arm.com> (raw)
In-Reply-To: <CAMn1gO4mKL4od8_4+RH9T2C+6+-7=rsdLrSNpghsbMyoVExCjA@mail.gmail.com>

On Tue, Feb 14, 2023 at 08:44:36PM -0800, Peter Collingbourne wrote:
> On Tue, Feb 14, 2023 at 9:54 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > If yes, I think we should use:
> >
> > Fixes: 20794545c146 ("arm64: kasan: Revert "arm64: mte: reset the page tag in page->flags"")
> > Cc: <stable@vger.kernel.org> # 6.0.x
> 
> I agree with the Fixes tag, but are you sure that 6.0.y is still
> supported as a stable kernel release? kernel.org only lists 6.1, and I
> don't see any updates to Greg's linux-6.0.y branch since January 12.

Yeah, that doesn't matter. I normally generate this with a git alias and
it matches the release containing the commit. I don't have to think
about which stable kernels are still maintained.

> I'm having some email trouble at the moment so I can't send a v2, so
> please feel free to add the Fixes tag yourself.

I can add the fixes tag.

-- 
Catalin

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

  reply	other threads:[~2023-02-15 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  1:52 [PATCH] arm64: Reset KASAN tag in copy_highpage with HW tags only Peter Collingbourne
2023-02-14  1:52 ` Peter Collingbourne
2023-02-14 17:54 ` Catalin Marinas
2023-02-14 17:54   ` Catalin Marinas
2023-02-15  4:44   ` Peter Collingbourne
2023-02-15  4:44     ` Peter Collingbourne
2023-02-15 13:46     ` Catalin Marinas [this message]
2023-02-15 13:46       ` Catalin Marinas
2023-02-17 10:05     ` Andrey Konovalov
2023-02-17 10:05       ` Andrey Konovalov

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=Y+ziGQAB3nhVqFY3@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Kuan-Ying.Lee@mediatek.com \
    --cc=Qun-wei.Lin@mediatek.com \
    --cc=andreyknvl@gmail.com \
    --cc=chinwen.chang@mediatek.com \
    --cc=eugenis@google.com \
    --cc=guangye.yang@mediatek.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=pcc@google.com \
    --cc=ryabinin.a.a@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=vincenzo.frascino@arm.com \
    --cc=will@kernel.org \
    /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.