search for: getmntent

I have a Fedora Core server running: Fedora Core release 4 (Stentz) kernel version: 2.6.15-1.1833_FC4smp ( I have also tried kernel version: 2.6.16-1.2108_FC4smp) I compiled the ocfs2 and ocfs2-tools using the following steps: # MODULES: tar zxvpf ocfs2-1.2.1.tar.gz cd ocfs2-1.2.1 ./configure make make install # TOOLS: tar zxf ocfs2-tools-1.2.1.tar.gz cd ocfs2-tools-1.2.1 ./configure

...lvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-15.10.tar.xz clang+llvm-3.8.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz On Ubuntu 16.04 x86_64: Failing Tests (7): MemorySanitizer :: Linux/forkpty.cc MemorySanitizer :: Linux/tcgetattr.cc MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.getmntent_r Profile :: instrprof-error.c Expected Passes...

...e review and on ack merge belows patchset. thanks maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: maximilian attems (8): [klibc] Add initial mntent.h with setmntent() and endmntent() [klibc] add getmntent() [klibc] mount: add help arg for usage() [klibc] mount: list all mounted file systems [klibc] mount: list fs of particular type [klibc] mount: read /proc/mounts preferably [klibc] ipconfig: raise field length for rootpath DHCP option [klibc] ipconfig: set null c...

[ gsi.de pretends this is massmailing so removed from CC's ] hello hpa, please review and on ack merge belows patchset. changes from v1, thanks to review by kzak: * add strtok_r() * use it in getmntent_r() * getment_r() parses mnt_freq and mnt_passno too isn't that hard. thanks maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: maximilian attems (9): [klibc] add strtok_r() [klibc] Add initial mntent.h with setmntent() and endmntent() [klibc] add ge...

.../boot /mnt/boot is device proc /usr/bin/extlinux: cannot open device proc But /mnt/boot is mounted on /dev/sda1 and ext3 file system. I read the source code and found the following code in install_loader() if ( (mtab = setmntent("/proc/mounts", "r")) ) { while ( (mnt = getmntent(mtab)) ) { if ( (!strcmp(mnt->mnt_type, "ext2") || !strcmp(mnt->mnt_type, "ext3")) && !stat(mnt->mnt_fsname, &dst) && dst.st_rdev == st.st_dev ) { devname = mnt->mnt_fsname; break; }...

...tizer-x86_64-linux :: TestCases/Posix/readv.cc MemorySanitizer :: Linux/tcgetattr.cc MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent_r MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent MemorySanitizer-Unit :: Msan-x86_64-with-call-Test/MemorySanitizer.gethostent_r MemorySanitizer-Unit :: Msan-x86_64-with-call-Tes...

...attr,dev=4700386 1184668792 Although there are two entries they have different device numbers. The mountpoint_get() function attempts to guard against this by checking the device number obtained matches that of the path being located. However for some reason I don't understand when getmntent() returns the FIRST of the above two entries it supplies the device number of the SECOND. Thus the device numbers match in the mountpoint_get() test and it thinks it has found the correct entry. This leads to the device_path being set to the map name -- auto_direct -- instead of the hos...

...59, 0] lib/util.c:smb_panic2(1482) PANIC: internal error [2004/12/21 15:54:59, 0] lib/util.c:smb_panic2(1490) BACKTRACE: 18 stack frames: #0 /usr/sbin/smbd(smb_panic2+0x120) [0x8202000] #1 /usr/sbin/smbd(smb_panic+0x26) [0x82021d6] #2 /usr/sbin/smbd [0x81ed0b0] #3 [0xffffe420] #4 /lib/tls/libc.so.6(getmntent+0x54) [0x4035ad84] #5 /usr/sbin/smbd [0x80e1058] #6 /usr/sbin/smbd(sys_get_quota+0xed) [0x80e1a7d] #7 /usr/sbin/smbd(disk_quotas+0x4d) [0x80e5aed] #8 /usr/sbin/smbd(sys_disk_free+0xcb) [0x8088bcb] #9 /usr/sbin/smbd(vfswrap_disk_free+0x39) [0x80d2329] #10 /usr/sbin/smbd [0x80ba8fb] #11 /usr/sbin/smb...

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release

...ic2(1495) PANIC: internal error [2005/06/06 16:56:22, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 22 stack frames: #0 smbd(smb_panic2+0x1bb) [0x81dcf83] #1 smbd(smb_panic+0x19) [0x81dcdc6] #2 smbd [0x81cac51] #3 smbd [0x81cacc6] #4 /lib/libc.so.6 [0x402b1168] #5 /lib/libc.so.6(__getmntent_r+0x36) [0x4035ed66] #6 /lib/libc.so.6(getmntent+0x55) [0x4035ec05] #7 smbd [0x80db11e] #8 smbd(sys_get_quota+0xa0) [0x80dba4e] #9 smbd(disk_quotas+0x46) [0x80df1ae] #10 smbd [0x8086a41] #11 smbd(sys_disk_free+0x2d) [0x8086ca8] #12 smbd(vfswrap_disk_free+0x2d) [0x80cac2c] #1...

...ux :: TestCases/Posix/readv.cc > MemorySanitizer :: Linux/tcgetattr.cc > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent_r > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.gethostent > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.gethostent_r > MemorySanitizer-Unit :: &g...

...TestCases/Posix/readv.cc > MemorySanitizer :: Linux/tcgetattr.cc > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.gethostent > MemorySanitizer-Unit :: Msan-x86_64- > Test/MemorySanitizer.gethostent_r > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent > MemorySanitizer-Unit :: Msan-x86_64-Test/MemorySanitizer.getmntent_r > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.gethostent > MemorySanitizer-Unit :: > Msan-x86_64-with-call-Test/MemorySanitizer.gethostent_r > MemorySanitizer-Unit :: Ms...

...006 17:15:01 -0000 @@ -358,7 +358,8 @@ AC_CHECK_FUNCS(fcntl flock lockf inet_aton sigaction getpagesize madvise \ strcasecmp stricmp vsnprintf vsyslog writev pread \ setrlimit setproctitle seteuid setreuid setegid setresgid \ - strtoull strtouq setpriority quotactl getmntent kqueue kevent) + strtoull strtouq setpriority quotactl getmntent kqueue kevent \ + getrusage) dnl * I/O loop function have_ioloop=no Index: src/lib/lib.h =================================================================== RCS file: /home/cvs/dovecot/src/lib/lib.h,v retrieving revis...

Dear testers, 3.7.0-rc2 was just tagged. Please test, build binaries, upload to the sftp, and report results to this thread. A lot of fixes have been applied since rc1, both to the build script and the code in general, so hopefully it will be less bumpy this time. >From this point, I will no longer accept merge requests to finish existing features; it's now bug-fixes only. Thanks again

Dear testers, 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: - r245902: Revert r245355: change of clang-tools-extra symlink in the release script - r245947: Merge of r245927: Fix LLDB build on MIPS - r245948: Deprecate the DataLayout on the TargetMachine, and backport the 3.8 API - Changes to the ReleaseNotes. Those changes should all be safe, and I expect this to be an extremely

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp

Dear testers, Release Candidate 2 has just been tagged [1]. Please build, test, and upload to the sftp. I know there are still outstanding issues from RC1, but there have been a lot of merges going into the branch and I think it's time for another round of RC testing. This RC comes a little behind schedule, sorry about that, but I'm still optimistic about hitting the target of releasing

...= find_device_mountinfo(path, st.st_dev); + devname = dupname(find_device_mountinfo(path, st.st_dev)); } #ifdef __KLIBC__ if (!devname) { - devname = find_device_sysfs(st.st_dev); + devname = dupname(find_device_sysfs(st.st_dev)); } if (!devname) { /* klibc doesn't have getmntent and friends; instead, just create @@ -1326,7 +1337,7 @@ static const char *get_devname(const char *path) } atexit(device_cleanup); /* unlink the device node on exit */ - devname = devname_buf; + devname = dupname(devname_buf); } #else @@ -1338,7 +1349,7 @@ static const char *get_devna...

...nl * after -lsocket and -lnsl tests, in AC_CHECK_FUNCS(fcntl flock lockf inet_aton sigaction getpagesize madvise \ strcasecmp stricmp vsnprintf vsyslog writev pread \ setrlimit setproctitle seteuid setreuid setegid setresgid \ - strtoull strtouq setpriority quotactl getmntent) + strtoull strtouq setpriority quotactl getmntent kqueue kevent) dnl * I/O loop function have_ioloop=no @@ -329,12 +329,17 @@ if test "$ioloop" = "epoll"; then fi if test "$ioloop" = "kqueue"; then - AC_CHECK_FUNC(kqueue, [ - AC_DEFINE(IOL...