On Tue, Oct 20, 2020 at 7:34 AM Dmitry Vyukov wrote:
>
> On Tue, Oct 20, 2020 at 12:51 AM Kostya Serebryany wrote:
> >
> > Hi,
> > I would like to hear opinions from others in CC on these choices:
> > * Production use of In-kernel MTE should be based on stripped-down
> > KASAN, or implemented ind
On Tue, Oct 20, 2020 at 12:51 AM Kostya Serebryany wrote:
>
> Hi,
> I would like to hear opinions from others in CC on these choices:
> * Production use of In-kernel MTE should be based on stripped-down
> KASAN, or implemented independently?
Andrey, what are the fundamental consequences of basing
On Mon, Oct 19, 2020 at 2:23 PM Marco Elver wrote:
>
> On Wed, 14 Oct 2020 at 22:44, Andrey Konovalov wrote:
> [...]
> > A question to KASAN maintainers: what would be the best way to support the
> > "off" mode? I see two potential approaches: add a check into each kasan
> > callback (easier to i
Hi,
I would like to hear opinions from others in CC on these choices:
* Production use of In-kernel MTE should be based on stripped-down
KASAN, or implemented independently?
* Should we aim at a single boot-time flag (with several values) or
for several independent flags (OFF/SYNC/ASYNC, Stack trac
On Wed, 14 Oct 2020 at 22:44, Andrey Konovalov wrote:
[...]
> A question to KASAN maintainers: what would be the best way to support the
> "off" mode? I see two potential approaches: add a check into each kasan
> callback (easier to implement, but we still call kasan callbacks, even
> though they
On Fri, Oct 16, 2020 at 3:31 PM Marco Elver wrote:
>
> On Fri, 16 Oct 2020 at 15:17, 'Andrey Konovalov' via kasan-dev
> wrote:
> [...]
> > > > The intention with this kind of a high level switch is to hide the
> > > > implementation details. Arguably, we could add multiple switches that
> > > >
On Thu, Oct 15, 2020 at 4:41 PM Marco Elver wrote:
>
> On Wed, 14 Oct 2020 at 22:44, Andrey Konovalov wrote:
> > This patchset is not complete (see particular TODOs in the last patch),
> > and I haven't performed any benchmarking yet, but I would like to start the
> > discussion now and hear peop
On Wed, Oct 14, 2020 at 10:44 PM Andrey Konovalov wrote:
>
> This patchset is not complete (see particular TODOs in the last patch),
> and I haven't performed any benchmarking yet, but I would like to start the
> discussion now and hear people's opinions regarding the questions mentioned
> below.
On Fri, 16 Oct 2020 at 15:17, 'Andrey Konovalov' via kasan-dev
wrote:
[...]
> > > The intention with this kind of a high level switch is to hide the
> > > implementation details. Arguably, we could add multiple switches that
> > > allow
> > > to separately control each KASAN or MTE feature, but I
On Thu, Oct 15, 2020 at 4:41 PM Marco Elver wrote:
>
> On Wed, 14 Oct 2020 at 22:44, Andrey Konovalov wrote:
> > This patchset is not complete (see particular TODOs in the last patch),
> > and I haven't performed any benchmarking yet, but I would like to start the
> > discussion now and hear peop
On Wed, 14 Oct 2020 at 22:44, Andrey Konovalov wrote:
> This patchset is not complete (see particular TODOs in the last patch),
> and I haven't performed any benchmarking yet, but I would like to start the
> discussion now and hear people's opinions regarding the questions mentioned
> below.
>
> =
This patchset is not complete (see particular TODOs in the last patch),
and I haven't performed any benchmarking yet, but I would like to start the
discussion now and hear people's opinions regarding the questions mentioned
below.
=== Overview
This patchset adopts the existing hardware tag-based
12 matches
Mail list logo
