* [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
@ 2020-09-24 4:01 Walter Wu
2020-09-24 11:51 ` Alexander Potapenko
2020-09-30 15:29 ` Thomas Gleixner
0 siblings, 2 replies; 10+ messages in thread
From: Walter Wu @ 2020-09-24 4:01 UTC (permalink / raw)
To: Andrew Morton, Thomas Gleixner, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Alexander Potapenko, Dmitry Vyukov, Andrey Konovalov,
Matthias Brugger
Cc: kasan-dev, linux-mm, linux-kernel, linux-arm-kernel,
wsd_upstream, linux-mediatek, Walter Wu
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.
[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
[3]https://bugzilla.kernel.org/show_bug.cgi?id=198437
Walter Wu (6):
timer: kasan: record timer stack
workqueue: kasan: record workqueue stack
kasan: print timer and workqueue stack
lib/test_kasan.c: add timer test case
lib/test_kasan.c: add workqueue test case
kasan: update documentation for generic kasan
---
Changes since v3:
- testcases have merge conflict, so that need to
be rebased onto the KASAN-KUNIT.
Changes since v2:
- modify kasan document to be readable,
Thanks for Marco suggestion.
Changes since v1:
- Thanks for Marco and Thomas suggestion.
- Remove unnecessary code and fix commit log
- reuse kasan_record_aux_stack() and aux_stack
to record timer and workqueue stack.
- change the aux stack title for common name.
---
Documentation/dev-tools/kasan.rst | 5 +++--
kernel/time/timer.c | 3 +++
kernel/workqueue.c | 3 +++
lib/test_kasan_module.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
mm/kasan/report.c | 4 ++--
5 files changed, 66 insertions(+), 4 deletions(-)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-09-24 4:01 [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN Walter Wu
@ 2020-09-24 11:51 ` Alexander Potapenko
2020-09-24 12:33 ` Walter Wu
2020-09-30 15:29 ` Thomas Gleixner
1 sibling, 1 reply; 10+ messages in thread
From: Alexander Potapenko @ 2020-09-24 11:51 UTC (permalink / raw)
To: Walter Wu
Cc: Andrew Morton, Thomas Gleixner, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Dmitry Vyukov, Andrey Konovalov, Matthias Brugger, kasan-dev,
Linux Memory Management List, LKML, Linux ARM, wsd_upstream,
linux-mediatek
> ---
> Documentation/dev-tools/kasan.rst | 5 +++--
> kernel/time/timer.c | 3 +++
> kernel/workqueue.c | 3 +++
> lib/test_kasan_module.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> mm/kasan/report.c | 4 ++--
> 5 files changed, 66 insertions(+), 4 deletions(-)
While at it, can you remove a mention of call_rcu() from the
kasan_record_aux_stack() implementation, as it is no more
RCU-specific?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-09-24 11:51 ` Alexander Potapenko
@ 2020-09-24 12:33 ` Walter Wu
0 siblings, 0 replies; 10+ messages in thread
From: Walter Wu @ 2020-09-24 12:33 UTC (permalink / raw)
To: Alexander Potapenko
Cc: Andrew Morton, Thomas Gleixner, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Dmitry Vyukov, Andrey Konovalov, Matthias Brugger, kasan-dev,
Linux Memory Management List, LKML, Linux ARM, wsd_upstream,
linux-mediatek
On Thu, 2020-09-24 at 13:51 +0200, 'Alexander Potapenko' via kasan-dev
wrote:
> > ---
> > Documentation/dev-tools/kasan.rst | 5 +++--
> > kernel/time/timer.c | 3 +++
> > kernel/workqueue.c | 3 +++
> > lib/test_kasan_module.c | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > mm/kasan/report.c | 4 ++--
> > 5 files changed, 66 insertions(+), 4 deletions(-)
>
> While at it, can you remove a mention of call_rcu() from the
> kasan_record_aux_stack() implementation, as it is no more
> RCU-specific?
>
Thank you for your reminder. v5 will do it.
Walter
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-09-24 4:01 [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN Walter Wu
2020-09-24 11:51 ` Alexander Potapenko
@ 2020-09-30 15:29 ` Thomas Gleixner
2020-12-01 7:59 ` Dmitry Vyukov
1 sibling, 1 reply; 10+ messages in thread
From: Thomas Gleixner @ 2020-09-30 15:29 UTC (permalink / raw)
To: Walter Wu, Andrew Morton, John Stultz, Stephen Boyd, Tejun Heo,
Lai Jiangshan, Marco Elver, Andrey Ryabinin, Alexander Potapenko,
Dmitry Vyukov, Andrey Konovalov, Matthias Brugger
Cc: kasan-dev, linux-mm, linux-kernel, linux-arm-kernel,
wsd_upstream, linux-mediatek, Walter Wu
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.
>
> [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?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-09-30 15:29 ` Thomas Gleixner
@ 2020-12-01 7:59 ` Dmitry Vyukov
2020-12-01 11:17 ` Walter Wu
2020-12-01 14:13 ` Thomas Gleixner
0 siblings, 2 replies; 10+ messages in thread
From: Dmitry Vyukov @ 2020-12-01 7:59 UTC (permalink / raw)
To: Thomas Gleixner
Cc: Walter Wu, Andrew Morton, John Stultz, Stephen Boyd, Tejun Heo,
Lai Jiangshan, Marco Elver, Andrey Ryabinin, Alexander Potapenko,
Andrey Konovalov, Matthias Brugger, kasan-dev, Linux-MM, LKML,
Linux ARM, wsd_upstream, linux-mediatek
On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@linutronix.de> 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 ;)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-12-01 7:59 ` Dmitry Vyukov
@ 2020-12-01 11:17 ` Walter Wu
2020-12-01 14:02 ` Dmitry Vyukov
2020-12-01 14:13 ` Thomas Gleixner
1 sibling, 1 reply; 10+ messages in thread
From: Walter Wu @ 2020-12-01 11:17 UTC (permalink / raw)
To: Dmitry Vyukov
Cc: Thomas Gleixner, Andrew Morton, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Alexander Potapenko, Andrey Konovalov, Matthias Brugger,
kasan-dev, Linux-MM, LKML, Linux ARM, wsd_upstream,
linux-mediatek
Hi Dmitry,
On Tue, 2020-12-01 at 08:59 +0100, 'Dmitry Vyukov' via kasan-dev wrote:
> On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@linutronix.de> 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.
>
Sorry for the delay in responding to this patch. I'm busy these few
months, so that suspend processing it.
Yes, I will send it next week. But v4 need to confirm the timer stack is
useful. I haven't found an example. Do you have some suggestion about
timer?
Thanks.
Walter
> > > [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 ;)
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-12-01 11:17 ` Walter Wu
@ 2020-12-01 14:02 ` Dmitry Vyukov
2020-12-02 1:22 ` Walter Wu
0 siblings, 1 reply; 10+ messages in thread
From: Dmitry Vyukov @ 2020-12-01 14:02 UTC (permalink / raw)
To: Walter Wu
Cc: Thomas Gleixner, Andrew Morton, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Alexander Potapenko, Andrey Konovalov, Matthias Brugger,
kasan-dev, Linux-MM, LKML, Linux ARM, wsd_upstream,
linux-mediatek
On Tue, Dec 1, 2020 at 12:17 PM Walter Wu <walter-zh.wu@mediatek.com> wrote:
>
> Hi Dmitry,
>
> On Tue, 2020-12-01 at 08:59 +0100, 'Dmitry Vyukov' via kasan-dev wrote:
> > On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@linutronix.de> 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.
> >
>
> Sorry for the delay in responding to this patch. I'm busy these few
> months, so that suspend processing it.
> Yes, I will send it next week. But v4 need to confirm the timer stack is
> useful. I haven't found an example. Do you have some suggestion about
> timer?
Good question.
We had some use-after-free's what mention call_timer_fn:
https://groups.google.com/g/syzkaller-bugs/search?q=%22kasan%22%20%22use-after-free%22%20%22expire_timers%22%20%22call_timer_fn%22%20
In the reports I checked call_timer_fn appears in the "access" stack
rather in the "free" stack.
Looking at these reports I cannot conclude that do_init_timer stack
would be useful.
I am mildly leaning towards not memorizing do_init_timer stack for now
(until we have clear use cases) as the number of aux stacks is very
limited (2).
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-12-01 14:02 ` Dmitry Vyukov
@ 2020-12-02 1:22 ` Walter Wu
0 siblings, 0 replies; 10+ messages in thread
From: Walter Wu @ 2020-12-02 1:22 UTC (permalink / raw)
To: Dmitry Vyukov
Cc: Thomas Gleixner, Andrew Morton, John Stultz, Stephen Boyd,
Tejun Heo, Lai Jiangshan, Marco Elver, Andrey Ryabinin,
Alexander Potapenko, Andrey Konovalov, Matthias Brugger,
kasan-dev, Linux-MM, LKML, Linux ARM, wsd_upstream,
linux-mediatek
On Tue, 2020-12-01 at 15:02 +0100, 'Dmitry Vyukov' via kasan-dev wrote:
> On Tue, Dec 1, 2020 at 12:17 PM Walter Wu <walter-zh.wu@mediatek.com> wrote:
> >
> > Hi Dmitry,
> >
> > On Tue, 2020-12-01 at 08:59 +0100, 'Dmitry Vyukov' via kasan-dev wrote:
> > > On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@linutronix.de> 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.
> > >
> >
> > Sorry for the delay in responding to this patch. I'm busy these few
> > months, so that suspend processing it.
> > Yes, I will send it next week. But v4 need to confirm the timer stack is
> > useful. I haven't found an example. Do you have some suggestion about
> > timer?
>
> Good question.
>
> We had some use-after-free's what mention call_timer_fn:
> https://groups.google.com/g/syzkaller-bugs/search?q=%22kasan%22%20%22use-after-free%22%20%22expire_timers%22%20%22call_timer_fn%22%20
> In the reports I checked call_timer_fn appears in the "access" stack
> rather in the "free" stack.
>
Yes, call stack already is useful for it in KASAN report.
> Looking at these reports I cannot conclude that do_init_timer stack
> would be useful.
> I am mildly leaning towards not memorizing do_init_timer stack for now
> (until we have clear use cases) as the number of aux stacks is very
> limited (2).
>
Got it. I will remove timer patch and send v5.
Thanks for your suggestion.
Walter
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-12-01 7:59 ` Dmitry Vyukov
2020-12-01 11:17 ` Walter Wu
@ 2020-12-01 14:13 ` Thomas Gleixner
2020-12-01 14:51 ` Dmitry Vyukov
1 sibling, 1 reply; 10+ messages in thread
From: Thomas Gleixner @ 2020-12-01 14:13 UTC (permalink / raw)
To: Dmitry Vyukov
Cc: Walter Wu, Andrew Morton, John Stultz, Stephen Boyd, Tejun Heo,
Lai Jiangshan, Marco Elver, Andrey Ryabinin, Alexander Potapenko,
Andrey Konovalov, Matthias Brugger, kasan-dev, Linux-MM, LKML,
Linux ARM, wsd_upstream, linux-mediatek
On Tue, Dec 01 2020 at 08:59, Dmitry Vyukov wrote:
> On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner <tglx@linutronix.de> 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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN
2020-12-01 14:13 ` Thomas Gleixner
@ 2020-12-01 14:51 ` Dmitry Vyukov
0 siblings, 0 replies; 10+ messages in thread
From: Dmitry Vyukov @ 2020-12-01 14:51 UTC (permalink / raw)
To: Thomas Gleixner
Cc: Walter Wu, Andrew Morton, John Stultz, Stephen Boyd, Tejun Heo,
Lai Jiangshan, Marco Elver, Andrey Ryabinin, Alexander Potapenko,
Andrey Konovalov, Matthias Brugger, kasan-dev, Linux-MM, LKML,
Linux ARM, wsd_upstream, linux-mediatek
On Tue, Dec 1, 2020 at 3:13 PM Thomas Gleixner <tglx@linutronix.de> 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.
Some random permissions settings changes were observed before, so I
can believe that.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-12-02 1:23 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-24 4:01 [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN Walter Wu
2020-09-24 11:51 ` Alexander Potapenko
2020-09-24 12:33 ` Walter Wu
2020-09-30 15:29 ` Thomas Gleixner
2020-12-01 7:59 ` Dmitry Vyukov
2020-12-01 11:17 ` Walter Wu
2020-12-01 14:02 ` Dmitry Vyukov
2020-12-02 1:22 ` Walter Wu
2020-12-01 14:13 ` Thomas Gleixner
2020-12-01 14:51 ` Dmitry Vyukov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).