From: Christian Hesse <list@eworm.de>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: general protection fault in css_release_work_fn()
Date: Mon, 3 May 2021 13:08:03 +0200 [thread overview]
Message-ID: <20210503130803.715a4477@leda> (raw)
In-Reply-To: <20210419125508.647ce682@leda>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Christian Hesse <list@eworm.de> on Mon, 2021/04/19 12:55:
> Hillf Danton <hdanton@sina.com> on Mo, 2021/04/12 16:05:
> > Looks like double free or use after free based on 0xdead.
> > If possible, would you try the mainline with KASAN enabled, given the fear
> > that few guys can find time for 5.10 this week?
>
> Currently running 5.11.13 with KASAN enabled for about a week. Either this
> has been fixed lately or I am suffering a race that does not happen with
> KASAN enabled.
Currently running 5.11.16 for about a week, looks stable now.
Still saw a crash with recent 5.10.x though... Looks like I have to build
that with KASAN.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-05-03 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 8:34 general protection fault in css_release_work_fn() Christian Hesse
2021-03-15 13:10 ` Christian Hesse
2021-04-12 6:20 ` Christian Hesse
[not found] ` <20210412080546.2098-1-hdanton@sina.com>
2021-04-19 10:55 ` Christian Hesse
2021-05-03 11:08 ` Christian Hesse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210503130803.715a4477@leda \
--to=list@eworm.de \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.