search for: namebuf

...[BUFSIZ]; >+ char ch, *cp, *np, *targ, *why, *vect[1], buf[BUFSIZ], path[PATH_MAX]; > > #define atime tv[0] > #define mtime tv[1] >@@ -686,21 +688,15 @@ > if (*cp++ != ' ') > SCREWUP("size not delimited"); > if (targisdir) { >- static char *namebuf = NULL; >- static size_t cursize; >- size_t need; >- >- need = strlen(targ) + strlen(cp) + 250; >- if (need > cursize) { >- if (namebuf != NULL) >- free(namebuf); >- if (!(namebuf = malloc(need))) >- run_err("%s", strerror(errno)); >-...

...ypXXX where XXX depends on the number of pseudo tty's entered in the scoadmin Tool for the network interface. So I change the allocation routine in the pty.c file from: snprintf(buf, sizeof buf, "/dev/pty%c%c", ptymajors[i / num_minors], ptyminors[i % num_minors]); snprintf(namebuf, namebuflen, "/dev/tty%c%c", ptymajors[i / num_minors], ptyminors[i % num_minors]); into: snprintf(buf, sizeof buf, "/dev/ptyp%d", i); snprintf(namebuf, namebuflen, "/dev/ttyp%d", i); 'i' is set in the for loop. I set 'i' to the maximum of...

...= lhread_u8(vcpu, (u64)name); + name = name + c + 1; + } + + return name - kstuff->names; +} + +static const char *lguest_syms_lookup(struct lguest_vcpu *vcpu, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset, + char **modname, char *namebuf) +{ + struct lguest_guest_info *linfo = vcpu->guest; + struct lguest_data *data = linfo->lguest_data; + struct guest_ksym_stuff kstuff; + const char *msym; + unsigned long *ptr; + int i; + + kstuff.addresses = (unsigned long*)lhread_u64(vcpu, (u64)&data->kallsyms_addresses); + kstuff.n...

...= lhread_u8(vcpu, (u64)name); + name = name + c + 1; + } + + return name - kstuff->names; +} + +static const char *lguest_syms_lookup(struct lguest_vcpu *vcpu, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset, + char **modname, char *namebuf) +{ + struct lguest_guest_info *linfo = vcpu->guest; + struct lguest_data *data = linfo->lguest_data; + struct guest_ksym_stuff kstuff; + const char *msym; + unsigned long *ptr; + int i; + + kstuff.addresses = (unsigned long*)lhread_u64(vcpu, (u64)&data->kallsyms_addresses); + kstuff.n...

...lgread_u8(lg, (unsigned long)name); + name = name + c + 1; + } + + return name - kstuff->names; +} + +static const char *lguest_syms_lookup(struct lguest *lg, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset, + char **modname, char *namebuf) +{ + struct lguest_data *data = lg->lguest_data; + struct guest_ksym_stuff kstuff; + const char *msym; + unsigned long *ptr; + int i; + + kstuff.addresses = (unsigned long*)lgread_u32(lg, + (unsigned long)&data->kallsyms_addresses); + kstuff.num_syms = lgread_u32(lg, (unsigned...

...lgread_u8(lg, (unsigned long)name); + name = name + c + 1; + } + + return name - kstuff->names; +} + +static const char *lguest_syms_lookup(struct lguest *lg, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset, + char **modname, char *namebuf) +{ + struct lguest_data *data = lg->lguest_data; + struct guest_ksym_stuff kstuff; + const char *msym; + unsigned long *ptr; + int i; + + kstuff.addresses = (unsigned long*)lgread_u32(lg, + (unsigned long)&data->kallsyms_addresses); + kstuff.num_syms = lgread_u32(lg, (unsigned...

...curity.", -}; - -static int copy_single_xattr(struct btrfs_trans_handle *trans, - struct btrfs_root *root, u64 objectid, - struct ext2_ext_attr_entry *entry, - const void *data, u32 datalen) -{ - int ret = 0; - int name_len; - int name_index; - void *databuf = NULL; - char namebuf[XATTR_NAME_MAX + 1]; - - name_index = entry->e_name_index; - if (name_index >= ARRAY_SIZE(xattr_prefix_table) || - xattr_prefix_table[name_index] == NULL) - return -EOPNOTSUPP; - name_len = strlen(xattr_prefix_table[name_index]) + - entry->e_name_len; - if (name_len >= sizeof(n...

Hey, So, I would be looking at type A. Forgive me if my understanding of how OpenSSH operates is not reflective of reality. I am assuming that, the file transfer is happening somewhat logically, with a name being known, content written, blah blah. >From reading scp.c, it appears that, the client end at least knows the file name so I must assume the server end must be given it. I am hoping to

...4_4) /* openpty(3) exists in OSF/1 and some other os'es */ - char buf[64]; + char *name; int i; - i = openpty(ptyfd, ttyfd, buf, NULL, NULL); + i = openpty(ptyfd, ttyfd, NULL, NULL, NULL); if (i < 0) { error("openpty: %.100s", strerror(errno)); return 0; } - strlcpy(namebuf, buf, namebuflen); /* possible truncation */ + name = ttyname(*ttyfd); + if (!name) + fatal("openpty returns device for which ttyname fails."); + + strlcpy(namebuf, name, namebuflen); /* possible truncation */ return 1; #else /* HAVE_OPENPTY */ #ifdef HAVE__GETPTY

...not necessarily be at the beginning + * of a function. + */ +static void __init populate_kprobe_blacklist(struct kprobe_blackpoint **start, + struct kprobe_blackpoint **end) { - int i, err = 0; + struct kprobe_blackpoint **iter, *bp; unsigned long offset = 0, size = 0; char *modname, namebuf[128]; const char *symbol_name; - void *addr; - struct kprobe_blackpoint *kb; + + for (iter = start; (unsigned long)iter < (unsigned long)end; iter++) { + bp = *iter; + symbol_name = kallsyms_lookup(bp->start_addr, + &size, &offset, &modname, namebuf); + if (!symbol_name) +...

...1; - } break; case sClientAliveInterval: * monitor_wrap.c:720:dead_error_line ? Execution cannot reach this statement "close(tmp2);".o --- a/monitor_wrap.c +++ b/monitor_wrap.c @@ -714,10 +714,8 @@ mm_pty_allocate(int *ptyfd, int *ttyfd, char *namebuf, size_t namebuflen) if ((tmp1 = dup(pmonitor->m_recvfd)) == -1 || (tmp2 = dup(pmonitor->m_recvfd)) == -1) { error("%s: cannot allocate fds for pty", __func__); - if (tmp1 > 0) + if (tmp1 > -1)...

...; + + *list_ret = newitem; + return 0; +} + + +/** + * Read the extended attributes for a file into an in-memory list. + * + * For symlinks we read the attributes of the link. + **/ +static int xa_load_list(char *filename, + struct xa_list **list_ret) +{ + char *namebuf; + size_t namebuf_len; + struct xa_list **pnext; + char *p, *end; + + *list_ret = NULL; + + if (xa_llistxattr_alloc(filename, &namebuf, &namebuf_len)) { + rprintf(FINFO, "failed to get attr list\n"); + return -1; /*...

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

Hi, I have found an serious problem when using 'scp -rp'. The usage of the static buffer "namebuf" together with calling `sink()' recursively results in overwriting the buffer np points to. This in turn results in a broken call to `ulimits()' and `chmod'. This patch solves the problem: Index: scp.c =================================================================== RCS file:...

Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() &

When running on PowerPC, we don''t have native PIO support. There are a few hacks around to enable PIO access on PowerPC nevertheless. The most typical one is the isa-mmio device. It takes MMIO requests and converts them to PIO requests on the (QEMU internal) PIO bus. This however is not how real hardware works and it limits us in the ability to spawn eventfd''s on PIO ports

...rnel_inittext(addr) ? (unsigned long)_einittext : (unsigned long)_etext; - *symbolsize = symbol_end - symbols_addresses[low]; - *offset = addr - symbols_addresses[low]; + *symbolsize = symbol_end - symbols_address(low); + *offset = addr - symbols_address(low); return namebuf; } --- 2009-07-10.orig/xen/common/symbols-dummy.c 2009-07-13 13:56:07.000000000 +0200 +++ 2009-07-10/xen/common/symbols-dummy.c 2009-06-30 16:55:43.000000000 +0200 @@ -6,11 +6,15 @@ #include <xen/config.h> #include <xen/types.h> -unsigned long symbols_addresses[1]; -unsigned long...

Hello, I would like to request an update of the progress regarding fixes for the recently disclosed SCP vulnerability (CVE-2018-20685, CVE-2019-6111, CVE-2019-6109, CVE-2019-6110) It has been stated that CVE-2018-20685 has been patched in november but there are currently no information available on the progress of patches regarding the other CVEs. Will there be a patched release any time soon?