[Bug 191151] [pam] Relative module path in PAM service description file does not work well
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191151 Dag-Erling Smørgrav changed: What|Removed |Added Status|Needs Triage|In Discussion Assignee|freebsd-bugs@FreeBSD.org|d...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192031] New: [ctl] link_elf_obj: symbol icl_pdu_new_bhs undefined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192031
Bug ID: 192031
Summary: [ctl] link_elf_obj: symbol icl_pdu_new_bhs undefined
Product: Base System
Version: 10.0-STABLE
Hardware: amd64
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: n...@renzel.net
Hi,
root@discofox:/usr/src/#uname -v
FreeBSD 10.0-STABLE #11 r268979M: Tue Jul 22 09:29:37 CEST 2014
root@discofox.local:/usr/obj/usr/src/sys/GENERIC
root@discofox:/usr/src/#svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/stable/10
Relative URL: ^/stable/10
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 268981
Node Kind: directory
Schedule: normal
Last Changed Author: jhb
Last Changed Rev: 268976
Last Changed Date: 2014-07-22 06:39:16 +0200 (Tue, 22 Jul 2014)
root@discofox:/usr/src/#svnlite diff
Index: sys/amd64/conf/GENERIC
===
--- sys/amd64/conf/GENERIC (revision 268981)
+++ sys/amd64/conf/GENERIC (working copy)
@@ -348,3 +348,9 @@
# VMware support
device vmx # VMware VMXNET3 Ethernet
+
+# VT
+nodevicesc
+nodevicevga
+device vt
+device vt_vga
Index: sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c
===
--- sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c (revision
268981)
+++ sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c (working copy)
@@ -78,7 +78,7 @@
assfail(const char *a, const char *f, int l)
{
- panic("solaris assert: %s, file: %s, line: %d", a, f, l);
+ printf("solaris assert: %s, file: %s, line: %d", a, f, l);
return (0);
}
@@ -88,6 +88,6 @@
const char *f, int l)
{
- panic("solaris assert: %s (0x%jx %s 0x%jx), file: %s, line: %d",
+ printf("solaris assert: %s (0x%jx %s 0x%jx), file: %s, line: %d",
a, lv, op, rv, f, l);
}
root@discofox:/usr/src/#kldload iscsi
root@discofox:/usr/src/#kldload ctl
kldload: an error occurred while loading the module. Please check dmesg(8) for
more details.
root@discofox:/usr/src/#dmesg -a | tail -10
iic15: on iicbus15
info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
info: [drm] Driver supports precise vblank timestamp query.
drmn0: taking over the fictitious range 0xc000-0xd000
fbd0 on drmn0
VT: Replacing driver "vga" with new "fb".
info: [drm] Initialized i915 1.6.0 20080730
Jul 22 14:08:27 discofox sshd[1141]: error: PAM: authentication error for root
from 10.2.0.7
link_elf_obj: symbol icl_pdu_new_bhs undefined
linker_load_file: Unsupported file type
root@discofox:/usr/src/#nm /boot/kernel/iscsi.ko | grep icl_pdu_new_bhs
3580 t icl_pdu_new_bhs
Regards,
Nils
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192032] New: [PATCH] savecore(8): Distinguish getbounds() errors; don't leak a FILE*
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192032 Bug ID: 192032 Summary: [PATCH] savecore(8): Distinguish getbounds() errors; don't leak a FILE* Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: conrad.me...@isilon.com Created attachment 144872 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144872&action=edit (apply with -p1 in src/) Minor: when fgets(3) fails in getbounds(), check for EOF and if not EOF, print strerror(3). Also, don't leak fp during non-error return (trivial since savecore(8) is not a long-running process anyway). Sponsored by:EMC / Isilon storage division -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192035] New: [PATCH] savecore(8): Be quiet unless the user asks for verbose
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192035 Bug ID: 192035 Summary: [PATCH] savecore(8): Be quiet unless the user asks for verbose Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: conrad.me...@isilon.com Created attachment 144875 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144875&action=edit ( -p1 in src/ ) Make savecore(8) more suitable for init-time scripts; be quiet by default. Sponsored by:EMC / Isilon storage division -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192036] New: [PATCH] Add error return to dumpsys(), use in doadump()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192036 Bug ID: 192036 Summary: [PATCH] Add error return to dumpsys(), use in doadump() Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: conrad.me...@isilon.com Created attachment 144876 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144876&action=edit ( apply with -p1 in source tree ) Add error return to dumpsys(), and use it in doadump(). Did not attempt to add error returns to minidumpsys() or textdump_dumpsys(); those can also be added later. Sponsored by:EMC / Isilon storage division -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192013] [xen] [pf] pf performance very bad in xen when tso enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192013 Dag-Erling Smørgrav changed: What|Removed |Added Attachment #144852|0 |1 is patch|| Attachment #144852|pf_xen_patch.txt|pf_xen_patch.diff filename|| Attachment #144852|pf_xen_patch.txt|Proposed patch description|| CC||d...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192013] [xen] [pf] pf performance very bad in xen when tso enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192013 Dag-Erling Smørgrav changed: What|Removed |Added Attachment #144852|0 |1 is obsolete|| Status|Needs Triage|In Discussion Assignee|freebsd-bugs@FreeBSD.org|d...@freebsd.org --- Comment #2 from Dag-Erling Smørgrav --- Created attachment 144883 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144883&action=edit More conservative patch When you say “TSO is disabled”, I assume you mean on the virtual interface (xnN) in the guest? I'm not comfortable removing this block of code without a clear understanding of why it's there. It looks to me like the intent is to ensure that all packets have a valid checksum before they enter pf. Are we certain that pf won't break in some subtle way if that assumption is violated? BTW, the patch does not remove the equivalent code in pf_check6_out(), but that code is broken anyway (as the comment points out). A more conservative fix is to keep calculating the checksum before pf_test *unless* hardware checksum offloading is enabled. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 137307] [libc] [patch] Enhance strptime(3) to support %U and %W
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137307 Pedro F. Giffuni changed: What|Removed |Added Attachment #98402|0 |1 is patch|| -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 137307] [libc] [patch] Enhance strptime(3) to support %U and %W
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137307 Pedro F. Giffuni changed: What|Removed |Added CC||p...@freebsd.org --- Comment #1 from Pedro F. Giffuni --- Created attachment 144894 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144894&action=edit Updated libc patch Thank you for contributing! The file has, of course, changed a lot. Still the support for %W and %U is very useful. We already have an isleap() macro in a header nearby that can be reused, for the rest I only did some style(9) fixes. I am not very good with the documentation so my change there is pretty minimal. I haven't tested it yet but I will. Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 137307] [libc] [patch] Enhance strptime(3) to support %U and %W
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137307
--- Comment #2 from Pedro F. Giffuni ---
(In reply to Pedro F. Giffuni from comment #1)
...
> I haven't tested it yet but I will.
>
Running test from:
http://www.scs.stanford.edu/histar/src/pkg/uclibc/test/time/tst-strptime.c
Results before the patch:
...
strptime ("2001 20 Mon", "%Y %U %a", ...)
should be: wday = 1, yday = 140, mon = 4, mday = 21
is: wday = 1, yday = 0, mon = 0, mday = 0
yearday for `2001 20 Mon' incorrect: 0 instead of 140
month for `2001 20 Mon' incorrect: 0 instead of 4
monthday for `2001 20 Mon' incorrect: 0 instead of 21
strptime ("2001 21 Mon", "%Y %W %a", ...)
should be: wday = 1, yday = 140, mon = 4, mday = 21
is: wday = 1, yday = 0, mon = 0, mday = 0
yearday for `2001 21 Mon' incorrect: 0 instead of 140
month for `2001 21 Mon' incorrect: 0 instead of 4
monthday for `2001 21 Mon' incorrect: 0 instead of 21
Results after the patch:
...
strptime ("2001 20 Mon", "%Y %U %a", ...)
should be: wday = 1, yday = 140, mon = 4, mday = 21
is: wday = 1, yday = 139, mon = 4, mday = 20
yearday for `2001 20 Mon' incorrect: 139 instead of 140
monthday for `2001 20 Mon' incorrect: 20 instead of 21
strptime ("2001 21 Mon", "%Y %W %a", ...)
should be: wday = 1, yday = 140, mon = 4, mday = 21
is: wday = 1, yday = 140, mon = 4, mday = 21
___
So there may be a technical mismatch (GNU libc manages to reinterpret standards
in amusing ways) for the %U case but the result is clearly a gain.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 137307] [libc] [patch] Enhance strptime(3) to support %U and %W
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137307 Pedro F. Giffuni changed: What|Removed |Added CC|p...@freebsd.org | Assignee|freebsd-bugs@FreeBSD.org|p...@freebsd.org Severity|Affects Only Me |Affects Some People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192010] sendbug program fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192010 Gavin Atkinson changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|ga...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192050] New: [zfs] The allowed character set for ZFS dataset names is very limited
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192050 Bug ID: 192050 Summary: [zfs] The allowed character set for ZFS dataset names is very limited Product: Base System Version: 10.0-RELEASE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: aberg...@my.hennepintech.edu While there are very few limitations on directory names, ZFS dataset names seem to support only alphanumeric characters and the space character. This is extremely annoying when trying to create the occasional dataset where the intended directory name has a punctuation mark such as an exclamation point. It also does not seem to support non-ASCII characters either. With the exception of @, I cannot see why a ZFS dataset name cannot support any character that is allowed in a directory name. With this limitation, there are two workarounds: limit directory names to the character set allowed in dataset names, or create different dataset names and explicitly set the mountpoint to have the correct name of the directory. The former is kind of absurd, but more or less manageable, depending on how badly you want/need the directory name to be correct. The latter creates the need for more complicated scripts and workflows, and extra permissions are needed for creating and mounting datasets with explicitly set mountpoints. # zfs create storage/文字化け cannot create 'storage/文字化け': invalid character ' in name # zfs create storage/touché cannot create 'storage/touché': invalid character ' in name # zfs create "storage/Here Today, Gone Tomorrow" cannot create 'storage/Here Today, Gone Tomorrow': invalid character ',' in name # zfs create "storage/Why?" cannot create 'storage/Why?': invalid character '?' in name I am quite curious why such a limitation exists. I would also like to know if this is a limitation of ZFS as a whole or just zfs(8) in particular. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192050] [zfs] The allowed character set for ZFS dataset names is very limited
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192050 Xin LI changed: What|Removed |Added Status|Needs Triage|Issue Resolved CC||delp...@freebsd.org Resolution|--- |Report to Upstream --- Comment #1 from Xin LI --- Please report this issue at upstream, at: https://www.illumos.org/projects/illumos-gate/issues/new We can not take unilateral action or we would risk creating incompatibility with other OpenZFS systems. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192050] [zfs] The allowed character set for ZFS dataset names is very limited
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192050 --- Comment #2 from Andrew Berg --- It's a bit confusing with the whole OpenZFS project going, but this would confirm my suspicion that illumos is still considered upstream. The upstream report, for reference: https://www.illumos.org/issues/5033 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 170320] [patch] adduser(8): usr.sbin/adduser/rmuser.sh It remains without erasing file `.*.cache'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170320 tak...@airport.fm changed: What|Removed |Added Status|In Discussion |Issue Resolved Resolution|--- |Not A Bug -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 170320] [patch] adduser(8): usr.sbin/adduser/rmuser.sh It remains without erasing file `.*.cache'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170320 --- Comment #1 from tak...@airport.fm --- `mail/qpopper' specific problems, rmuser (1) is no problem. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
