Displaying 20 results from an estimated 30000 matches similar to: "Possible memory corruption in virtio-pci driver."
2016 Jan 14
0
Possible memory corruption in virtio-pci driver.
On Thu, Jan 14, 2016 at 02:25:50PM +0100, Jerome Marchand wrote:
> Hi Michael,
>
> KASan detected a use-after-free error in virtio-pci remove code. In
> virtio_pci_remove(), vp_dev is still used after being freed in
> unregister_virtio_device() (in virtio_pci_release_dev() more
> precisely). I don't know the proper way to fix this.
Thanks a lot for the report, I posted a
2018 Aug 05
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
On 25/07/2018 10:59 PM, David Miller wrote:
> From: "Michael S. Tsirkin" <mst at redhat.com>
> Date: Wed, 25 Jul 2018 12:40:12 +0300
>
>> On Mon, Jul 23, 2018 at 11:36:03PM +0900, Toshiaki Makita wrote:
>>> From: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp>
>>>
>>> Add some ethtool stat items useful for performance analysis.
2018 Aug 05
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
On 25/07/2018 10:59 PM, David Miller wrote:
> From: "Michael S. Tsirkin" <mst at redhat.com>
> Date: Wed, 25 Jul 2018 12:40:12 +0300
>
>> On Mon, Jul 23, 2018 at 11:36:03PM +0900, Toshiaki Makita wrote:
>>> From: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp>
>>>
>>> Add some ethtool stat items useful for performance analysis.
2019 Aug 23
1
[PATCH] drm/nouveau: Fix memory leak in nvkm_ram_get()
When resuming from ACPI S3, memory leak happens in nvkm_ram_get().
This is because *pmemory points to newly allocated memory without
checking and freeing the old memory.
Here is the log showing this issue.
unreferenced object 0xffffa3b608c6d5c0 (size 64):
comm "kworker/u32:30", pid 934, jiffies 4294823520 (age 5000.217s)
hex dump (first 32 bytes):
00 fc 4a c0 ff ff ff ff 00 00
2018 Jul 31
1
KASAN: use-after-free Read in vhost_transport_send_pkt
On Mon, Jul 30, 2018 at 11:15:03AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: acb1872577b3 Linux 4.18-rc7
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14eb932c400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2dc0cd7c2eefb46f
> dashboard link:
2007 Apr 18
1
[Bridge] Unexpected bridge behavior (Bug? You decide.)
While using the linux bridge module in 2.6.10, the kernel seems to
munge the source IP address of broadcast UDP packets if they come from
"0.0.0.1", and sticks on an address of the linux host.
I humbly submit that re-writing the source address of packets is not
proper behavior for a bridge, even if those source addresses are not
traditionally valid.
Sure, 0.0.0.1 isn't a valid
2016 Nov 07
3
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Hi,
I can relatively easily reproduce this bug:
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
------------[ cut here ]------------
kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 355 Comm: kworker/1:2 Not tainted 4.9.0-rc2-next-20161028+ #32
Hardware name: QEMU Standard PC (i440FX
2016 Nov 07
3
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Hi,
I can relatively easily reproduce this bug:
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
------------[ cut here ]------------
kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 355 Comm: kworker/1:2 Not tainted 4.9.0-rc2-next-20161028+ #32
Hardware name: QEMU Standard PC (i440FX
2018 Nov 27
2
[2.3.4] Segmentation faults
It's still missing core dump (or bt full from it)
Aki
On 27.11.2018 8.39, Joan Moreau wrote:
>
> Thank you Aki
>
> here the requested data (below)
>
> Please not as well that we have numerous subfolders (>50) and pretty
> big mailbox sizes (>20G)
>
> Bug appears mostly in auth process and index-worker
>
>
> dovecot -n :
>
> # 2.4.devel
2018 Nov 25
3
[2.3.4] Segmentation faults
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 25 November 2018 at 06:29 Joan Moreau <
<a href="mailto:jom@grosjo.net">jom@grosjo.net</a>> wrote:
</div>
<div>
2018 Nov 28
2
[2.3.4] Segmentation faults
See https://dovecot.org/bugreport.html#coredumps
Without a backtrace it's not really possible to figure out where it's crashing.
> On 28 Nov 2018, at 13.20, Joan Moreau <jom at grosjo.net> wrote:
>
> Where to get that ?
>
>
> On 2018-11-27 08:50, Aki Tuomi wrote:
>
>> It's still missing core dump (or bt full from it)
>>
>> Aki
2005 Oct 21
1
Xen unstable: Cannot ping gateway, ping dom0 to domU vice versa ok
Hi,
I hope someone could help me out. Pls find the details below.
dom0: ifconfig before "xend start"
eth0 Link encap:Ethernet HWaddr 00:0C:76:53:44:FB
inet addr:10.0.0.3 <http://10.0.0.3> Bcast:10.0.0.255 <http://10.0.0.255>Mask:
255.255.255.0 <http://255.255.255.0>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX
2018 Mar 21
2
AMI potential memory leak
We are communicating with Asterisk via AMI. Running Asterisk version 13.18.5 on an Ubuntu box.
If you look at the event response, the Result field is filled with random characters. I'm not sure what to do because that is a completely random result. It makes no sense.
We send the following command to asterisk via AMI
Action: AGI
ActionID: C44415
Channel: SIP/192.168.40.105-00001338
2017 Nov 24
1
SSL configuration
Hello subscribers,
I have a very strange question regarding SSL setup on gluster storage.
I have create a common CA and sign certificate for my gluster nodes, placed host certificate, key and common CA certificate into /etc/ssl/,
create a file called secure-access into /var/lib/glusterd/
Then, I start glusterd on all nodes, system work fine, I see with peer status all of my nodes.
No problem.
2017 Jul 15
4
[drm/nouveau] GeForce 8600 GT boot/suspend grumbling
Greetings,
box: bog standard [tc]rusty old Nvidia equipped Q6600 Medion (Aldi) deskside
kernel: master.today (v4.12-11690-gccd5d1b91f22)
lspci -nn -d 10de:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1)
abreviated dmesg:
...
[ 3.720990] fb: switching to nouveaufb from VESA VGA
[ 3.744489] Console: switching to colour dummy device
2014 Jan 03
7
[Bug 73267] New: Nouveau: corrupted laptop screen's EDID info
https://bugs.freedesktop.org/show_bug.cgi?id=73267
Priority: medium
Bug ID: 73267
Assignee: nouveau at lists.freedesktop.org
Summary: Nouveau: corrupted laptop screen's EDID info
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: ezelspinguin at
2017 Dec 12
5
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
Has anyone seen this recently? I couldn't replicate it on:
- CentOS 6 running kernel-2.6.32-696.16.1.el6.x86_64,
kernel-lt-4.4.105-1.el6.elrepo.x86_64
- CentOS 7 running 4.9.67-1.el7.centos.x86_64
But I can replicate it consistently running "xl -v vcpu-set <domU>
<val>" on:
- CentOS 6 running 4.14.5-1.el6.elrepo.x86_64
- CentOS 7 running 4.14.5-1.el7.elrepo.x86_64
2017 Feb 15
3
[PATCH net-next] virito-net: set queues after reset during xdp_set
We set queues before reset which will cause a crash[1]. This is
because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
number to do the correct detection. So fix this by:
- set queues after reset, to keep the old vi->curr_queue_pairs. (in
fact setting queues before reset does not works since after feature
set, all queue pairs were enabled by default during reset).
- change
2017 Feb 15
3
[PATCH net-next] virito-net: set queues after reset during xdp_set
We set queues before reset which will cause a crash[1]. This is
because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
number to do the correct detection. So fix this by:
- set queues after reset, to keep the old vi->curr_queue_pairs. (in
fact setting queues before reset does not works since after feature
set, all queue pairs were enabled by default during reset).
- change
2005 Sep 18
4
Just a simple question (I think)
Hi all,
How do I put a rule in to allow all ports on a single IP..
I''m not masq my network as the firewall is on the router.
I have another firewall internally that I will be removing sometime soon,
but just wish to forward all ports to this firewall (until I can
decommission it).
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether