[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKA=qzarDypzsgbvgfvwVYLnUPw1QBjHK9KMhHZE3fopEtrXmg@mail.gmail.com>
Date: Thu, 16 Nov 2017 15:24:46 -0800
From: Josh Hunt <joshhunt00@...il.com>
To: "Levin, Alexander" <alexander.levin@...izon.com>
Cc: Julia Lawall <julia.lawall@...6.fr>,
Laura Abbott <labbott@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>
Subject: Re: [PATCH 4.9 086/104] arm64: kasan: avoid bad virt_to_pfn()
On Thu, Nov 16, 2017 at 3:13 PM, <alexander.levin@...izon.com> wrote:
>
> It's possible, but I didn't want to add a bunch of clutter to the
> commit message. Right now it's somewhat easy to track it back to
> automatic selection because:
>
> 1. I'm signed off on all of them, so I could chime in in the case
> concerns/issues arise with a patch.
> 2. They all have a corresponding review request email with the
> AUTOSEL marker.
>
I get the want to not clutter the commit logs. My comment was more
directed to a few weeks or months after the patch has made it into a
stable release. At that point I'm not sure the person who found the
problem with the change would know to CC you on any correspondence, or
even if the author of the change would know to contact you. Although I
guess maybe they'd eventually track things down and report to stable,
or Greg, or something else and it would eventually get back to you.
--
Josh
Powered by blists - more mailing lists