public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: linux-kernel@vger.kernel.org
Subject: Re: general protection fault in css_release_work_fn()
Date: Mon, 15 Mar 2021 14:10:38 +0100	[thread overview]
Message-ID: <20210315141038.1cc59f54@leda> (raw)
In-Reply-To: <20210302093415.7b463ddc@leda>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Hello everybody,

Christian Hesse <list@eworm.de> on Tue, 2021/03/02 09:34:
> I see this on a git server with lots of ssh logins. It happens every few
> hours to days. No idea how to reproduce, guess it's a race condition?
> 
> general protection fault, probably for non-canonical address
> 0xdead000000000122: 0000 [#1] SMP NOPTI CPU: 3 PID: 2213757 Comm:
> kworker/3:2 Not tainted 5.10.18-1-lts #1

I've seen more crashes with 5.10.23-1-lts and 5.11.6-arch1-1. Looks like
5.11.2-arch1-1 is stable for now, but I did not test everything in between.

Anybody has an idea what commit could have caused this?
-- 
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 --]

  reply	other threads:[~2021-03-15 13:11 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 [this message]
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

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=20210315141038.1cc59f54@leda \
    --to=list@eworm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox