diff for duplicates of <1bffad2d-db13-9808-afc9-5594f02dcf01@gmail.com> diff --git a/a/1.txt b/N1/1.txt index fe8cab5..5aaff36 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -43,49 +43,4 @@ On 12/12/19 1:24 am, Daniel Axtens wrote: > those instrumentations only work/make sense with a static offset, but > perhaps that's not right? Dmitry and Andrey, can you shed some light on > this? -> - -From what I can read, everything should still be supported, the info page -for gcc states that globals, stack asan should be enabled by default. -allocas may have limited meaning if stack-protector is turned on (no?) - -> Also, as it currently stands, the speed difference between inline and -> outline is approximately 2x, and given that we'd like to run this -> full-time in syzkaller I think there is value in trading off speed for -> some limitations. -> - -Full speed vs actually working across different configurations? - ->> BTW, the current set of patches just hang if I try to make the default ->> mode as out of line -> -> Do you have CONFIG_RELOCATABLE? -> -> I've tested the following process: -> -> # 1) apply patches on a fresh linux-next -> # 2) output dir -> mkdir ../out-3s-kasan -> -> # 3) merge in the relevant config snippets -> cat > kasan.config << EOF -> CONFIG_EXPERT=y -> CONFIG_LD_HEAD_STUB_CATCH=y -> -> CONFIG_RELOCATABLE=y -> -> CONFIG_KASAN=y -> CONFIG_KASAN_GENERIC=y -> CONFIG_KASAN_OUTLINE=y -> -> CONFIG_PHYS_MEM_SIZE_FOR_KASAN=2048 -> EOF -> - -I think I got CONFIG_PHYS_MEM_SIZE_FOR_KASN wrong, honestly I don't get why -we need this size? The size is in MB and the default is 0. - -Why does the powerpc port of KASAN need the SIZE to be explicitly specified? - -Balbir Singh. +> diff --git a/a/content_digest b/N1/content_digest index a20a784..8b63c03 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -67,51 +67,6 @@ "> those instrumentations only work/make sense with a static offset, but\n" "> perhaps that's not right? Dmitry and Andrey, can you shed some light on\n" "> this?\n" - "> \n" - "\n" - "From what I can read, everything should still be supported, the info page\n" - "for gcc states that globals, stack asan should be enabled by default.\n" - "allocas may have limited meaning if stack-protector is turned on (no?)\n" - "\n" - "> Also, as it currently stands, the speed difference between inline and\n" - "> outline is approximately 2x, and given that we'd like to run this\n" - "> full-time in syzkaller I think there is value in trading off speed for\n" - "> some limitations.\n" - "> \n" - "\n" - "Full speed vs actually working across different configurations?\n" - "\n" - ">> BTW, the current set of patches just hang if I try to make the default\n" - ">> mode as out of line\n" - "> \n" - "> Do you have CONFIG_RELOCATABLE?\n" - "> \n" - "> I've tested the following process:\n" - "> \n" - "> # 1) apply patches on a fresh linux-next\n" - "> # 2) output dir\n" - "> mkdir ../out-3s-kasan\n" - "> \n" - "> # 3) merge in the relevant config snippets\n" - "> cat > kasan.config << EOF\n" - "> CONFIG_EXPERT=y\n" - "> CONFIG_LD_HEAD_STUB_CATCH=y\n" - "> \n" - "> CONFIG_RELOCATABLE=y\n" - "> \n" - "> CONFIG_KASAN=y\n" - "> CONFIG_KASAN_GENERIC=y\n" - "> CONFIG_KASAN_OUTLINE=y\n" - "> \n" - "> CONFIG_PHYS_MEM_SIZE_FOR_KASAN=2048\n" - "> EOF\n" - "> \n" - "\n" - "I think I got CONFIG_PHYS_MEM_SIZE_FOR_KASN wrong, honestly I don't get why\n" - "we need this size? The size is in MB and the default is 0. \n" - "\n" - "Why does the powerpc port of KASAN need the SIZE to be explicitly specified?\n" - "\n" - Balbir Singh. + > -3f6e786615aa70b7c211e310b536cb4548b2a9593af739733b7f9c6256981787 +9c43d699caeddc47f79873e9fec76b579e90088102421a1d6e35e9dc873b801c
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox