search for: inbuf

...bfffaf88) at loop.c:282 #1 0xb7f9cbb2 in __gconv_transform_ascii_internal (step=0x80a2ee8, data=0x80a2fe8, inptrp=0xbfffb05c, inend=0xbfffbd48 "\n", outbufstart=0x0, irreversible=0xbfffb018, do_flush=0, consume_incomplete=0) at skeleton.c:483 #2 0xb7f99ec7 in __gconv (cd=0x80a2fe0, inbuf=0xbfffb05c, inbufend=0xbfffbd48 "\n", outbuf=0xbfffb064, outbufend=0x80a3d24 "", irreversible=0xbfffb018) at gconv.c:63 #3 0xb7f996fc in iconv (cd=0x80a2fe0, inbuf=0xbfffb05c, inbytesleft=0xbfffb060, outbuf=0xbfffb064, outbytesleft=0xbfffb068) at iconv.c:53 #4 0x08050f6d in ic...

...mp;& ic_send == (iconv_t)-1) #endif convert = 0; #ifdef ICONV_OPTION /* We need to convert buf before doing anything else so that we * can include the (converted) byte length in the message header. */ if (convert) { xbuf outbuf, inbuf; INIT_XBUF(outbuf, buffer + 4, 0, sizeof(buffer) - 4); INIT_XBUF(inbuf, (char*)buf, len, -1); iconvbufs(ic_send, &inbuf, &outbuf, ICB_INCLUDE_BAD | ICB_INCLUDE_INCOMPLETE); if (inbuf.len &gt...

...al port even though there were messages queued up there. I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from inbuf through port_fops_read, to empty the current port->inbuf, port->inbuf will be NULL even though there may be buffers left in the virtqueue. This causes poll() to block even though there is da...

...al port even though there were messages queued up there. I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from inbuf through port_fops_read, to empty the current port->inbuf, port->inbuf will be NULL even though there may be buffers left in the virtqueue. This causes poll() to block even though there is da...

From: Hans de Goede <hdegoede at redhat.com> I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from inbuf through port_fops_read, to empty the current port->inbuf, port->inbuf will be NULL even though there may be buffers left in the virtqueue. This causes poll() to block even though there is da...

From: Hans de Goede <hdegoede at redhat.com> I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from inbuf through port_fops_read, to empty the current port->inbuf, port->inbuf will be NULL even though there may be buffers left in the virtqueue. This causes poll() to block even though there is da...

...rtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 kernel error: virtio-ports vport2p2: Error allocating inbufs qemu error: virtio-serial-bus: Guest failure in adding port 2 for device \ virtio-serial0.0 This happens because buffers for the in_vq are allocated when the port is added but are not released when the port is unplugged. They are only released when virtconsole is removed (...

...rtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 kernel error: virtio-ports vport2p2: Error allocating inbufs qemu error: virtio-serial-bus: Guest failure in adding port 2 for device \ virtio-serial0.0 This happens because buffers for the in_vq are allocated when the port is added but are not released when the port is unplugged. They are only released when virtconsole is removed (...

...n */ 0x68, 0, 0x42, 0x32, 0x31, 0 }; /**************************************************************************** attempted support for server level security ****************************************************************************/ BOOL server_validate(char *buf, char *user) { pstring inbuf,outbuf; BOOL ret; if (password_client < 0) { DEBUG(1,("%s not connected\n",pserver)); return(False); } bzero(inbuf,sizeof(inbuf)); memcpy(outbuf,buf,sizeof(outbuf)); /* send a session setup command */ CVAL(outbuf,smb_flg) = 0x8; SSVAL(outbuf,smb_flg2,0x1)...

Hi all, Thanks to Wayne and Park, I''ve got something like this now: static VALUE file_set_compressed(VALUE self, VALUE rbBool){ HANDLE h; BOOL rv; DWORD dwBytesReturned; int fn; USHORT inBuf = COMPRESSION_FORMAT_DEFAULT; if((rbBool != Qtrue) && (rbBool != Qfalse)){ rb_raise(rb_eTypeError,"Argument must be true or false"); } if(rbBool == Qfalse){ inBuf = COMPRESSION_FORMAT_NONE; } fn = NUM2INT(rb_funcall(self,rb_intern("fileno...

...chardev=serial0,id=serial0,name=serial0 >> (qemu) device_del serial0 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >> chardev=serial0,id=serial0,name=serial0 >> kernel error: >> virtio-ports vport2p2: Error allocating inbufs >> qemu error: >> virtio-serial-bus: Guest failure in adding port 2 for device \ >> virtio-serial0.0 >> >> This happens because buffers for the in_vq are allocated when the port is >> added but are not released when the port is unplugged....

...chardev=serial0,id=serial0,name=serial0 >> (qemu) device_del serial0 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >> chardev=serial0,id=serial0,name=serial0 >> kernel error: >> virtio-ports vport2p2: Error allocating inbufs >> qemu error: >> virtio-serial-bus: Guest failure in adding port 2 for device \ >> virtio-serial0.0 >> >> This happens because buffers for the in_vq are allocated when the port is >> added but are not released when the port is unplugged....

...0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > (qemu) device_del serial0 > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > kernel error: > virtio-ports vport2p2: Error allocating inbufs > qemu error: > virtio-serial-bus: Guest failure in adding port 2 for device \ > virtio-serial0.0 > > This happens because buffers for the in_vq are allocated when the port is > added but are not released when the port is unplugged. > > They are onl...

...ial0,id=serial0,name=serial0 > >> (qemu) device_del serial0 > >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > >> chardev=serial0,id=serial0,name=serial0 > >> kernel error: > >> virtio-ports vport2p2: Error allocating inbufs > >> qemu error: > >> virtio-serial-bus: Guest failure in adding port 2 for device \ > >> virtio-serial0.0 > >> > >> This happens because buffers for the in_vq are allocated when the port is > >> added but are not release...

...roper file_fsp( smb_vwv0) when doing an IOCTL request.This causes the file_fsp call in reply_ioctl (smbd/reply.c) to fail cause a segmentation fault. I do not understand how samba work, but here is my working patch for this. I just copied the fid from the last open_And_X call and write it into inbuf if the file_fsp is different. Attached here is the diff. The patch is only on /smbd/reply.c Thank you. Iskantharajah T -------------- next part -------------- --- ./reply.c Mon Apr 7 09:54:00 2003 +++ reply.c.new Fri Sep 5 19:38:51 2003 @@ -45,6 +45,10 @@ Report a possible attack via t...

To make it complete, here is the code that I am using to encode a large file: int __stdcall SpxEncode(unsigned char* inBuf, unsigned char* outBuf, unsigned int inlen) { //char *testFile; //FILE *ftest; //testFile = "test"; //ftest = fopen(testFile, "wb"); //fwrite(inBuf,1,inlen,ftest); //take every 320 bytes //copy every short to float array, and make sure to put...

https://bugzilla.samba.org/show_bug.cgi?id=11338 Bug ID: 11338 Summary: Rsync Crash - Segmentation fault Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Is it safe to change the inbuf[1025] to something larger... Like double it??? I understand this is just for my use- I'm not asking for a code base change. I have longer "variables" that I need to pass. Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.co...

...th/auth_util.c:1308 #13 0x0809841c in user_in_list (user=0xbfffe8e0 "DELSOLW2K\\Dale", list=0x83ef350) at smbd/password.c:520 #14 0x08094002 in map_username (user=0xbfffe8e0 "DELSOLW2K\\Dale") at smbd/map_username.c:162 #15 0x080bece7 in reply_spnego_kerberos (conn=0x0, inbuf=0x407ab008 "", outbuf=0x407cc008 "", length=1458, bufsize=131072, secblob=0xbfffeb60) at smbd/sesssetup.c:292 #16 0x080bfc05 in reply_spnego_negotiate (conn=0x0, inbuf=0x407ab008 "", outbuf=0x407cc008 "", vuid=100, length=1458, bufsize=131072, b...

...0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > (qemu) device_del serial0 > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > kernel error: > virtio-ports vport2p2: Error allocating inbufs > qemu error: > virtio-serial-bus: Guest failure in adding port 2 for device \ > virtio-serial0.0 > > This happens because buffers for the in_vq are allocated when the port is > added but are not released when the port is unplugged. > > They are onl...