On Tue, Dec 01 2020 at 08:59, Dmitry Vyukov wrote: > On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: >> On Thu, Sep 24 2020 at 12:01, Walter Wu wrote: >> > Syzbot reports many UAF issues for workqueue or timer, see [1] and [2]. >> > In some of these access/allocation happened in process_one_work(), >> > we see the free stack is useless in KASAN report, it doesn't help >> > programmers to solve UAF on workqueue. The same may stand for times. >> > >> > This patchset improves KASAN reports by making them to have workqueue >> > queueing stack and timer stack information. It is useful for programmers >> > to solve use-after-free or double-free memory issue. >> > >> > Generic KASAN also records the last two workqueue and timer stacks and >> > prints them in KASAN report. It is only suitable for generic KASAN. > > Walter, did you mail v5? > Checking statuses of KASAN issues and this seems to be not in linux-next. > >> > [1]https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22+process_one_work >> > [2]https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22%20expire_timers >> >> How are these links useful for people who do not have a gurgle account? > > This is a public mailing list archive, so effectively the same way as > lore links ;) Just that it asked me to log in last time. That's why I wrote the above. Today it does not, odd. Thanks, tglx