similar to: memory leak in vhost_net_ioctl

Displaying 20 results from an estimated 200 matches similar to: "memory leak in vhost_net_ioctl"

2019 Jun 14
0
memory leak in vhost_net_ioctl
Hello, syzbot has tested the proposed patch but the reproducer still triggered crash: memory leak in batadv_tvlv_handler_register 484.626788][ T156] bond0 (unregistering): Releasing backup interface bond_slave_1 Warning: Permanently added '10.128.0.87' (ECDSA) to the list of known hosts. BUG: memory leak unreferenced object 0xffff88811d25c4c0 (size 64): comm
2019 Jun 14
0
memory leak in vhost_net_ioctl
Hello Syzbot On Fri, 14 Jun 2019 11:04:03 +0800 syzbot wrote: > >Hello, > >syzbot has tested the proposed patch but the reproducer still triggered crash: >memory leak in batadv_tvlv_handler_register > It is not ubuf leak which is addressed in this thread. Good news. I will see this new leak soon. > 484.626788][ T156] bond0 (unregistering): Releasing backup interface
2019 Jun 14
0
memory leak in vhost_net_ioctl
Hello Syzbot On Fri, 14 Jun 2019 11:04:03 +0800 syzbot wrote: > >Hello, > >syzbot has tested the proposed patch but the reproducer still triggered crash: >memory leak in batadv_tvlv_handler_register > > 484.626788][ T156] bond0 (unregistering): Releasing backup interface bond_slave_1 >Warning: Permanently added '10.128.0.87' (ECDSA) to the list of known hosts.
2019 Jun 13
2
memory leak in vhost_net_ioctl
Hello Dmitry On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote: > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton <hdanton at sina.com> wrote: > > > > Hello Jason > > > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote: > > > > > > This is basically a kfree(ubuf) after the second vhost_net_flush() in > > > vhost_net_release(). >
2019 Jun 13
2
memory leak in vhost_net_ioctl
Hello Dmitry On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote: > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton <hdanton at sina.com> wrote: > > > > Hello Jason > > > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote: > > > > > > This is basically a kfree(ubuf) after the second vhost_net_flush() in > > > vhost_net_release(). >
2019 Jun 06
1
memory leak in vhost_net_ioctl
On Wed, 05 Jun 2019 16:42:05 -0700 (PDT) syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: 788a0249 Merge tag 'arc-5.2-rc4' of git://git.kernel.org/p.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=15dc9ea6a00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d5c73825cbdc7326
2019 Jun 06
1
memory leak in vhost_net_ioctl
On Wed, 05 Jun 2019 16:42:05 -0700 (PDT) syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: 788a0249 Merge tag 'arc-5.2-rc4' of git://git.kernel.org/p.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=15dc9ea6a00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d5c73825cbdc7326
2019 Jun 05
0
memory leak in vhost_net_ioctl
Hello, syzbot found the following crash on: HEAD commit: 788a0249 Merge tag 'arc-5.2-rc4' of git://git.kernel.org/p.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15dc9ea6a00000 kernel config: https://syzkaller.appspot.com/x/.config?x=d5c73825cbdc7326 dashboard link: https://syzkaller.appspot.com/bug?extid=0789f0c7e45efd7bb643 compiler: gcc
2019 Jun 13
0
memory leak in vhost_net_ioctl
On 2019/6/6 ??10:40, Hillf Danton wrote: > > On Wed, 05 Jun 2019 16:42:05 -0700 (PDT) syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:??? 788a0249 Merge tag 'arc-5.2-rc4' of >> git://git.kernel.org/p.. >> git tree:?????? upstream >> console output:
2019 Jun 13
0
memory leak in vhost_net_ioctl
On Thu, Jun 13, 2019 at 4:15 PM Hillf Danton <hdanton at sina.com> wrote: > > > Hello Dmitry > > On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote: > > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton <hdanton at sina.com> wrote: > > > > > > Hello Jason > > > > > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote: > >
2006 May 23
11
how to debug RTNETLINK invalid argument?
Hey, I am getting an invalid argument trying to insert a qdisc: [root@emu-5 iproute2]# tc qdisc add dev eth0 root xcp capacity 50Mbit limit 500 RTNETLINK answers: Invalid argument I''m not sure whats wrong here, because i can successfully insert this qdisc on other computers of mine. How can i debug this? Thanks! George
2003 Mar 04
6
ip rule nat
when doing somehitng like ip rule add fwmark 3 nat 200.42.75.183 table ppp0 prio 1 (the idea is that packets that match the fwmark 3 change their source address to 200.42.75.183)..it first apply the nat and then routes to table ppp0 right? in such case the, nat, why may be nat not being applyed? cause it doesnt work at all..it goes to that interface but does not nat the src address of the package.
2015 Feb 11
2
Problems in SAMBA 3.3 to 4.0 migration
Hi, Rowland, and thanks for the reply. The PDC OS is Slackware 13. The BDC OS is Slackware 14. The choice to use Samba 4.0 was merely due to its inclusion on the Slackware 14 distro. I'll worry about upgrading that once I have the migration complete. I will post the two machine's respective smb.conf's later today. -- View this message in context:
2011 Nov 16
2
Where is source address info of a route kept?
I have an ethernet device in my lan with a primary address 192.168.5.205 and a secondary address .217. I added the secondary address after network startup established the primary address by an ip addr add command: # ip addr add 192.168.5.217/24 broadcast 192.168.5.255 dev eth0 # ip addr show ... 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether
2002 Oct 23
23
"basic two-interface" setup problem
Hi, I installed the shorewall 1.3.8-2 debian package to my debian testing machine which serves as the gateway to the internet. Since I have two other machine connect to internet thru this gateway machine, I also downloaded the configuration guide for "basic two-interface firewall" and followed the instructions. When I try to start the shorewall I get the following message and can not
2015 Jan 03
2
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, i am really depressed at this moment. I set up an domain controller using samba4 and an raspberry pi. I can join the domain and everything works BUT kerberos has some strange problems resolving my raspberry hostname. First of all some information: Raspberry pi is DHCP Server and DNS-Server (BIND9). First of all the configurations: Code: /usr/local/samba/etc/smb.conf # Global
2015 Jan 03
2
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, /etc/resolv.conf looks exactly like this: domain family.rapsberry.local search family.rapsberry.local nameserver 192.168.178.222 So to answer your question: yes the only Nameserver the raspberry has is itself. Greetings Am 2015-01-03 um 7:40 PM schrieb Rowland Penny: > On 03/01/15 16:31, Robert Hartmann wrote: >> Hi, >> >> i am really depressed at this moment. I set
2010 Mar 13
1
klibc build trouble
as the next klibc release 1.5.16 looks like shaping up, I have a trouble to build that for Debian. currently I build depent on linux-libc-dev, I don't know what against I can build latest klibc, see klibc fails to build due too: make -C linux/ ARCH=x86_64 INSTALL_HDR_PATH=debian/tmp/usr/lib/klibc/ headers_install make[3]: *** No rule to make target `headers_install'. Stop. make[2]: ***
2015 Jan 03
1
Samba4 Kerberos kinit does not resolve kdc hostname
Hi, thank you so! much. Turning off avahi daemon was the solution! rapsberry instead of raspberry is a typo during porivision actually. Thank you again :) I will write an entry on my blog to make sure that does not happen again. One last time for google bots. IF you receive kinit: Cannot contact any KDC for realm while getting initial credentials make sure you don't run avahi However
2018 Jul 26
2
net-next boot error
On Thu, Jul 26, 2018 at 11:29 AM, syzbot <syzbot+604f8271211546f5b3c7 at syzkaller.appspotmail.com> wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: dc66fe43b7eb rds: send: Fix dead code in rds_sendmsg > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=127874c8400000 > kernel config: