[Bug 230720] strptime() conversion and validation issues

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230720

--- Comment #3 from rlit...@inetco.com  ---
Many thanks, Yuri.

Ralph

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 221777] merge the latest changes to the ig4 module from DragonFly BSD and add Kaby Lake / Intel 100 series platform support

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221777

Neel Chauhan  changed:

   What|Removed |Added

 CC||n...@neelc.org

--- Comment #28 from Neel Chauhan  ---
I have tried this on a HP EliteBook 1040 G3 and while the touchpad was
detected, I could not move the cursor. psm works on the 1040 G3 as an Alps
GlidePoint (the 1040 G3 uses the Alps T4 chip) but I cannot do things like two
finger scroll. The T4 chip supports HID over I2C and I think this is a better
place to support the T4 than psm (keep in mind that I am no expert on pointing
devices or the FreeBSD kernel).

dmesg reports this:

acpi_iichid0:  on acpi0
acpi_iichid0: descriptor register address is 20
acpi_iichid0: unexpected type 17 while parsing Current Resource Settings (_CSR)
acpi_iichid0: parent device is "\134_SB_.PCI0.I2C1"
iichid0:  at addr 0x20 on iicbus1
iichid0: ADDR 0x20 REG 0x20
iichid0: 3 buttons and [XYZ] coordinates ID=6
iichid0: 3 buttons and [XYZ] coordinates ID=6
acpi_iichid0: added iichid0 ADDR 0x20 REG 0x20 to iicbus1
acpi_iichid0: could not allocate IRQ resource

The last line seems interesting.

If I start moused and point at /dev/ims0, I get this error:

moused: unable to get status of mouse fd: Inappropriate ioctl for device

And am unable to move the cursor. However, /dev/ims0 does exist.

A Linux patch for Alps T4 is here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73196ebe134d11a68a2e27814c489d685cfc8b03

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 30321] [patch] strftime(3) '%s' format does not work properly

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=30321

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@yuripv.net

--- Comment #5 from Yuri Pankov  ---
(17 years later) this behavior now looks like being there forever, and glibc
agrees, likely we can close this?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 192016] Incorrect result for %s in strftime

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192016

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@yuripv.net

--- Comment #1 from Yuri Pankov  ---
It's hard to say if it's a bug in FreeBSD libc and glibc or if it's a bug in
musl as %s is NOT specified by POSIX.  See bug #30321 for more details.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 230720] strptime() conversion and validation issues

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230720

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@yuripv.net

--- Comment #2 from Yuri Pankov  ---
"00","%d" is fixed in base r339241 (bug #232072)
"00","%I" and "00","%l" are fixed in base r339346.

I'll take care of the remaining issues reported here, and sorry for missing
this initially.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 231882] multiple toolchain issues with statically linked binaries

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231882
Bug 231882 depends on bug 232176, which changed state.

Bug 232176 Summary: elftoolchain elfcopy/strip incorrectly strips relocations
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232176

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 232176] elftoolchain elfcopy/strip incorrectly strips relocations

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232176

Ed Maste  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 232176] elftoolchain elfcopy/strip incorrectly strips relocations

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232176

--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:

Author: emaste
Date: Sat Oct 13 21:26:07 UTC 2018
New revision: 339350
URL: https://svnweb.freebsd.org/changeset/base/339350

Log:
  elfcopy: delete filter_reloc, it is broken and unnecessary

  elfcopy contained logic to filter individual relocations in STRIP_ALL
  mode.  However, this is not valid; relocations emitted by the linker are
  required, unless they apply to an entire section being removed (which is
  handled by other logic in elfcopy).

  Note that filter_reloc was also buggy: for RELA relocation sections it
  operated on uninitialized rel.r_info resulting in invalid operation.

  The logic most likely needs to be inverted: instead of removing
  relocations because their associated symbols are being removed, we must
  keep symbols referenced by relocations.  That said, in practice we do
  not encounter this code path today: objects being stripped are either
  dynamically linked binaries which retain .dynsym, or static binaries
  with no relocations.

  Just remove filter_reloc.  This fixes certain cases including statically
  linked binaries containing ifuncs.  Stripping binaries with relocations
  referencing removed symbols was already broken, and after this change
  may still be broken in a different way.

  PR:   232176
  Reviewed by:  kaiw, kib, markj
  Approved by:  re (rgrimes)
  MFC after:1 month
  Sponsored by: The FreeBSD Foundation
  Differential Revision:https://reviews.freebsd.org/D17519

Changes:
  head/contrib/elftoolchain/elfcopy/sections.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 229830] [truss] throws an assertion failure after the trussed process got killed

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229830

--- Comment #4 from Jan Kokemüller  ---
Sorry, I forgot to mention that I'm running FreeBSD 12.0-ALPHA9 amd64 with some
local patches:
FreeBSD 12.0-ALPHA9 FreeBSD 12.0-ALPHA9 #3
r339331+0547250df758(test-suspend48)-dirty: Sat Oct 13 13:47:25 CEST 2018

With the program I posted it is reproducible ~80-90% of the time on my laptop.
I've found that adding a "usleep(5);" between the pthread_create() and
kill() increases this number. This makes sure that "truss -H" gets the new
thread notification (like "101702: ").

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 232210] sendfile(2) doesn't percolate up issues with copyout(9) related to sbytes

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232210

Gleb Smirnoff  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|gleb...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 232210] sendfile(2) doesn't percolate up issues with copyout(9) related to sbytes

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232210

Gleb Smirnoff  changed:

   What|Removed |Added

 Status|New |In Progress

--- Comment #2 from Gleb Smirnoff  ---
That's a good catch, but I don't fully agree on the patch. Some return values
of sendfile aren't errors, and the patch doesn't cover them. If sendfile
returns EAGAIN, which is normal for non-blocking socket, we again ignore
copyout error. I think we should take in copyout error always.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 178664] truss(1) may kill process

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178664

Alan Somers  changed:

   What|Removed |Added

 CC||asom...@freebsd.org

--- Comment #5 from Alan Somers  ---
Can we close this, Jilles?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 229830] [truss] throws an assertion failure after the trussed process got killed

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229830

Alan Somers  changed:

   What|Removed |Added

 Status|New |Open

--- Comment #3 from Alan Somers  ---
I can reproduce this on 11.2-RELEASE and TrueOS-Desktop-201803131015, but not
12.0-ALPHA9.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Classic Gear Priced to Sell

2018-10-13 Thread Denmark Street Guitars
[[HEADLINE]]

[[PERMALINK_FULL_LINK]]







TITLE OF YOUR EMAIL

The content of your email goes here.

You can drag and drop blocks of text, images or other content elements to add 
them to your message. Customize the font and the colors. Add links to track 
clicks.







This is a second paragraph you can customize as your please.

If you have stored contact properties with your contacts, you can include 
personalization variables such as first name, last name in your message content.



[[DELIVERY_INFO]]
[[POSTAL_ADDRESS]]
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 229830] [truss] throws an assertion failure after the trussed process got killed

2018-10-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229830

Jan Kokemüller  changed:

   What|Removed |Added

 CC||jan.kokemuel...@gmail.com

--- Comment #2 from Jan Kokemüller  ---
This bug can be reproduced by truss'ing  this process:


#include 

#include 
#include 
#include 

void *thread_fun(void *arg) {
(void)arg;

sleep(5);

return NULL;
}

int main() {
pthread_t thread;

if (pthread_create(, NULL, thread_fun, NULL) != 0) {
return 1;
}

kill(getpid(), SIGKILL);

sleep(1);
}


I suspect the reason is that threads killed by "thread_single()" in "exit1()"
don't send a ptrace notification.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"