On Tue, Feb 19, 2019 at 2:43 PM Nick Desaulniers
wrote:
>
> + Evgenii, Kostya for KASAN
>
> On Tue, Feb 19, 2019 at 2:17 PM Qian Cai wrote:
> >
> > On Tue, 2019-02-19 at 22:49 +0100, Arnd Bergmann wrote:
> > > Building an arm64 allmodconfig kernel with clang results in over 140
> > > warnings
>
On Wed, Feb 20, 2019 at 1:40 PM Arnd Bergmann wrote:
>
> On Wed, Feb 20, 2019 at 10:13 PM Arnd Bergmann wrote:
> >
> > In the example in https://bugs.llvm.org/show_bug.cgi?id=38809#c12
> > (https://godbolt.org/z/ylsGSQ) there is no inlining, yet clang uses
> > over ten times as much stack space a
On Wed, Feb 20, 2019 at 2:12 PM Kostya Serebryany wrote:
>
> On Wed, Feb 20, 2019 at 1:40 PM Arnd Bergmann wrote:
> >
> > On Wed, Feb 20, 2019 at 10:13 PM Arnd Bergmann wrote:
> > >
> > > In the example in https://bugs.llvm.org/show_bug.cgi?id=38809#c12
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
The boot parameters look great!
Do we use redzones in kasan.mode=prod?
(I think we should not)
Please separate the work on improving the stack trace collection form the work
on enabling kasan.mode=prod, the latter is more important IMHO.
Still some notes on stack traces:
> kasan.mode=full has 4
> >
> > I believe this would only be an output bit, but I'm not sure how it
> > would be wired into binutils. Kostya, do you know any details about
> > how AddressSanitizer might be able to create this ELF note?
I don't, hopefully H.J's suggestion works.
Will it be backward compatible?
(i.e. will
6 matches
Mail list logo