mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bronek Kozicki <brok@incorrekt.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: cgroups@vger.kernel.org
Subject: Re: PROBLEM: NULL pointer dereference in kernel 4.14.6
Date: Sun, 17 Dec 2017 18:48:16 +0000	[thread overview]
Message-ID: <1513536496.3754736.1207944032.00C6D43E@webmail.messagingengine.com> (raw)
In-Reply-To: <54a16e07-70e6-adda-ebdb-06349b4f8e86@infradead.org>

FWIW, I can do "cat" . I get a single number seemingly followed by an
infinite stream of 0s (I tried wc -l, but did not want to wait very long
and killed it). Here is what it looks like, if limited by "head":

root@gdansk ~ # cat
'/sys/fs/cgroup/unified/machine.slice/machine-qemu\x2d1\x2dkartuzy\x2dspice.scope/cgroup.procs'
| head
10649
0
0
0
0
0
0
0
0
0
root@gdansk ~ #

PID 10649 is indeed qemu process running the virtual machine in
question:

root@gdansk ~ # ps lw 10649
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME
COMMAND
6     0 10649     1  20   0 4815836 60252 -     Sl   ?          2:56
/usr/bin/qemu-system-x86_64 -name
guest=kartuzy-spice,process=qemu:kartuzy-spice,debug-threads=on -S
-object se


Sorry about taint by ZFS, but there is nothing I can do, it is my root
filesystem. Since I am the only user of the package in question I could
cheat and replace the license for the build of the ZFS module, but I do
not see how that might help.


B.

  parent reply	other threads:[~2017-12-17 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 12:14 Bronek Kozicki
2017-12-17 13:29 ` Bronek Kozicki
2017-12-17 17:49   ` Bronek Kozicki
2017-12-17 18:25     ` Randy Dunlap
2017-12-17 18:30       ` Bronek Kozicki
2017-12-17 18:31         ` Randy Dunlap
2017-12-17 18:48       ` Bronek Kozicki [this message]
2017-12-17 23:24     ` vcaputo
2017-12-18 19:56       ` Bronek Kozicki
2017-12-19 13:42       ` Tejun Heo
2017-12-20 15:14         ` Tejun Heo
2017-12-20 18:04           ` Bronek Kozicki
2017-12-18 20:17 George Amanakis
2017-12-19 22:37 ` Tejun Heo

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=1513536496.3754736.1207944032.00C6D43E@webmail.messagingengine.com \
    --to=brok@incorrekt.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®