diff options
author | Kees Cook <[email protected]> | 2019-05-30 23:37:29 -0700 |
---|---|---|
committer | Kees Cook <[email protected]> | 2019-05-31 01:19:06 -0700 |
commit | 8880fa32c557600f5f624084152668ed3c2ea51e (patch) | |
tree | 94b3238af77f6aba43ad030947ad6b81d4174bfe /net/unix/sysctl_net_unix.c | |
parent | a9fb94a99bb515d8720ba8440ce3aba84aec80f8 (diff) |
pstore/ram: Run without kernel crash dump region
The ram pstore backend has always had the crash dumper frontend enabled
unconditionally. However, it was possible to effectively disable it
by setting a record_size=0. All the machinery would run (storing dumps
to the temporary crash buffer), but 0 bytes would ultimately get stored
due to there being no przs allocated for dumps. Commit 89d328f637b9
("pstore/ram: Correctly calculate usable PRZ bytes"), however, assumed
that there would always be at least one allocated dprz for calculating
the size of the temporary crash buffer. This was, of course, not the
case when record_size=0, and would lead to a NULL deref trying to find
the dprz buffer size:
BUG: unable to handle kernel NULL pointer dereference at (null)
...
IP: ramoops_probe+0x285/0x37e (fs/pstore/ram.c:808)
cxt->pstore.bufsize = cxt->dprzs[0]->buffer_size;
Instead, we need to only enable the frontends based on the success of the
prz initialization and only take the needed actions when those zones are
available. (This also fixes a possible error in detecting if the ftrace
frontend should be enabled.)
Reported-and-tested-by: Yaro Slav <[email protected]>
Fixes: 89d328f637b9 ("pstore/ram: Correctly calculate usable PRZ bytes")
Cc: [email protected]
Signed-off-by: Kees Cook <[email protected]>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions