Displaying 20 results from an estimated 8000 matches similar to: "[Bug 1036] BUG: unable to handle kernel NULL pointer dereference at ... nf_nat_setup_info"
2020 Jan 10
0
[Bug 1036] BUG: unable to handle kernel NULL pointer dereference at ... nf_nat_setup_info
https://bugzilla.netfilter.org/show_bug.cgi?id=1036
Pablo Neira Ayuso <pablo at netfilter.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
CC|
2017 Jan 10
2
CentOS 7: BUG: unable to handle kernel NULL pointer dereference
We've just started seeing this. Anyone else?
reason: BUG: unable to handle kernel NULL pointer dereference at
00000000000000b8
component: kernel
count: 1
analyzer: vmcore
architecture: x86_64
event_log:
kernel: 3.10.0-327.18.2.el7.x86_64
last_occurrence: 1484067452
os_release: CentOS Linux release 7.3.1611 (Core)
runlevel: N 3
time:
2017 Jan 10
0
CentOS 7: BUG: unable to handle kernel NULL pointer dereference
Am 10.01.2017 um 19:51 schrieb m.roth at 5-cent.us:
> We've just started seeing this. Anyone else?
>
> reason: BUG: unable to handle kernel NULL pointer dereference at
> 00000000000000b8
> component: kernel
> count: 1
> analyzer: vmcore
> architecture: x86_64
> event_log:
> kernel: 3.10.0-327.18.2.el7.x86_64
>
2017 Mar 25
1
NVAC - BUG: unable to handle kernel NULL pointer dereference
With lightweight desktoping,
the atomic modesetting seems far from robust.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000021
IP: dma_fence_wait_timeout+0x36/0xf0
...
Oops: 0000 [#1] SMP
Modules linked in: ... nouveau ...
CPU: 0 PID: 6895 Comm: Xorg Not tainted 4.10.5-1001.fc24.x86_64 #1
...
Call Trace:
drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
2017 Oct 15
6
[Bug 103284] New: Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp
https://bugs.freedesktop.org/show_bug.cgi?id=103284
Bug ID: 103284
Summary: Unable to handle kernel NULL pointer dereference on
4.13.0-1-sparc64-smp
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component:
2013 May 12
9
[Bug 818] New: BUG: unable to handle kernel NULL pointer dereference at 0000020c (ipt_log_packet+0x2e/0x2b0)
https://bugzilla.netfilter.org/show_bug.cgi?id=818
Summary: BUG: unable to handle kernel NULL pointer dereference
at 0000020c (ipt_log_packet+0x2e/0x2b0)
Product: netfilter/iptables
Version: unspecified
Platform: i386
OS/Version: Gentoo
Status: NEW
Severity: normal
Priority: P5
2018 Jan 12
3
[Bug 104609] New: [G96, 9500 GT] Removing nouveau module results in BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
https://bugs.freedesktop.org/show_bug.cgi?id=104609
Bug ID: 104609
Summary: [G96, 9500 GT] Removing nouveau module results in BUG:
unable to handle kernel NULL pointer dereference at
00000000000000b8
Product: Mesa
Version: unspecified
Hardware: All
OS: All
Status: NEW
2010 Apr 10
11
[Bug 27574] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
https://bugs.freedesktop.org/show_bug.cgi?id=27574
Summary: BUG: unable to handle kernel NULL pointer dereference
at 0000000000000028
Product: xorg
Version: 7.5
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2018 Mar 20
12
[Bug 105626] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
https://bugs.freedesktop.org/show_bug.cgi?id=105626
Bug ID: 105626
Summary: BUG: unable to handle kernel NULL pointer dereference
at 0000000000000040
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
2018 Mar 22
7
[Bug 105687] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000ca0
https://bugs.freedesktop.org/show_bug.cgi?id=105687
Bug ID: 105687
Summary: BUG: unable to handle kernel NULL pointer dereference
at 0000000000000ca0
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component:
2012 May 04
2
btrfs scrub BUG: unable to handle kernel NULL pointer dereference
I think I have some failing hard drives, they are disconnected for now.
stan {~} root# btrfs filesystem show
Label: none uuid: d71404d4-468e-47d5-8f06-3b65fa7776aa
Total devices 2 FS bytes used 6.27GB
devid 1 size 9.31GB used 8.16GB path /dev/sde6
*** Some devices missing
Label: none uuid: b142f575-df1c-4a57-8846-a43b979e2e09
Total devices 8 FS bytes used
2011 Dec 07
3
WARNING: at fs/btrfs/extent-tree.c:4754 followed by BUG: unable to handle kernel NULL pointer dereference at (null)
Hello btrfs!
Recently I upgraded to 3.2.0-rc4 due to instabilities with my btrfs
filesystem in 3.1.1. While with 3.1.1 my system completely froze, with
3.2.0-rc4 it stays at least somehow usable (for some strange reason my xorg
screen turns black as soon as this happens, only ssh is working then).
Scrubbing reports 1 uncorrectable error. I have this error since my system
froze due to some
2012 May 09
0
[LLVMdev] Null pointer dereference
Hi Yury,
No need for the "{" "}" since it's a single statement in the compound statement. Other than that minor style detail, this looks fine assuming it applies cleanly to trunk.
Do you have commit access?
Regards,
-Jim
On May 9, 2012, at 3:40 PM, Yury Mikhaylov wrote:
> Hi all,
>
> Writing my own LLVM client I've noticed a potential null pointer
2012 May 09
1
[LLVMdev] Null pointer dereference
Thank you for your response Jim.
As of revision 153342 it applies properly to trunk. No, unfortunately I
don't have access, would you please commit it for me?
Thanks,
Yury
On Wed, May 9, 2012 at 4:37 PM, Jim Grosbach <grosbach at apple.com> wrote:
> Hi Yury,
>
> No need for the "{" "}" since it's a single statement in the compound
> statement.
2018 Feb 20
0
[Bug 105173] [MCP79][Regression] Unhandled NULL pointer dereference in nvkm_object_unmap since kernel 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=105173
Pierre Moreau <pierre.morrow at free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[MCP79][Regression] |[MCP79][Regression]
|Unhandled NULL pointer |Unhandled NULL pointer
2016 Aug 21
0
[PATCH 1/1] virtio-gpu: avoid possible NULL pointer dereference
If output is NULL it is not permissable to dereference it.
So we should leave the respective function in this case.
The inconsistency was indicated by cppcheck.
No actual NULL pointer dereference was observed.
Signed-off-by: Heinrich Schuchardt <xypron.glpk at gmx.de>
---
drivers/gpu/drm/virtio/virtgpu_plane.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
2016 Aug 21
0
[PATCH 1/1] virtio-gpu: avoid possible NULL pointer dereference
If output is NULL it is not permissable to dereference it.
So we should leave the respective function in this case.
The inconsistency was indicated by cppcheck.
No actual NULL pointer dereference was observed.
Signed-off-by: Heinrich Schuchardt <xypron.glpk at gmx.de>
---
drivers/gpu/drm/virtio/virtgpu_plane.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
2023 Oct 07
1
[PATCH] drm/nouveau/dispnv04: fix a possible null pointer dereference
In nv17_tv_get_ld_modes(), the return value of drm_mode_duplicate()
is assigned to mode, which will lead to a NULL pointer dereference
on failure of drm_mode_duplicate(). Add a check to avoid npd.
Signed-off-by: Ma Ke <make_ruc2021 at 163.com>
---
drivers/gpu/drm/nouveau/dispnv04/tvnv17.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/dispnv04/tvnv17.c
2023 Oct 13
1
[PATCH] drm/nouveau/dispnv04: fix a possible null pointer dereference
In nv17_tv_get_hd_modes(), the return value of drm_mode_duplicate()
is assigned to mode, which will lead to a NULL pointer dereference on
failure of drm_mode_duplicate(). The same applies to drm_cvt_mode().
Add a check to avoid null pointer dereference.
Signed-off-by: Ma Ke <make_ruc2021 at 163.com>
---
drivers/gpu/drm/nouveau/dispnv04/tvnv17.c | 4 ++++
1 file changed, 4 insertions(+)
2012 May 09
2
[LLVMdev] Null pointer dereference
Hi all,
Writing my own LLVM client I've noticed a potential null pointer
dereference in EngineBuilder::selectTarget.
The class has an optional pointer to the ErrorStr, which can be initialzied
through setErrorStr() method. Although, it's strictly optional,
selectTarget doesn't verify its value before assignment.
Please find patch for branch release_31, revision 155051 attached.
-