[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Thu Dec 17 19:51:39 UTC 2020 New revision: 368735 URL: https://svnweb.freebsd.org/changeset/base/368735 Log: Fix a race in tty_signal_sesslea

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #6 from Jakub Piecuch --- (In reply to Konstantin Belousov from comment #5) I mention t_session in the comment because it contains the mutex that we should be holding in order to access t_session->s_leader. proctree_lock would a

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #5 from Konstantin Belousov --- (In reply to Jakub Piecuch from comment #4) You talked about a race with zeroing s_leader, but comment now mention t_session. I reformulated the comment, and also read t_session into local, just

[Bug 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #11 from Vladimir Kondratyev --- Created attachment 220675 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220675&action=edit Fix for the "kernel bug: device has min == max on ABS_X" libinput-related issue Try attache

[Bug 243401] ahci driver problems with Marvell 88SE9230 (Dell BOSS-S1)

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243401 Peter Eriksson changed: What|Removed |Added Version|11.3-RELEASE|12.2-RELEASE --- Comment #3 from

[Bug 244906] kernel booted by loader.efi on VMware Fusion crashes in EFI firmware

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244906 --- Comment #16 from Yuri Pankov --- (In reply to Yuri Pankov from comment #14) sorry, bad copy/paste :( -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bug

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 Yuri Pankov changed: What|Removed |Added CC||fdup...@isc.org --- Comment #16 from

[Bug 244906] kernel booted by loader.efi on VMware Fusion crashes in EFI firmware

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244906 --- Comment #15 from Yuri Pankov --- *** This bug has been marked as a duplicate of bug 251866 *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@fr

[Bug 251918] strptime(): %b always returns month 0

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251918 Yuri Pankov changed: What|Removed |Added CC||fdup...@isc.org --- Comment #3 from

[Bug 244906] kernel booted by loader.efi on VMware Fusion crashes in EFI firmware

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244906 Yuri Pankov changed: What|Removed |Added CC||yur...@freebsd.org Statu

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #15 from YUAN RUI --- It seems to increase the size for compatibility with the nvidia driver, but if it is reduced back, the nvidia driver cannot be loaded? -- You are receiving this mail because: You are the assignee for the

[Bug 251918] strptime(): %b always returns month 0

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251918 --- Comment #2 from Yuri Pankov --- (In reply to Yuri Pankov from comment #1) Actually, "as it comes earlier" part is not correct; it seems to be implementation choice as standard does not specify was happens if conflicting specifiers are p

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #4 from Jakub Piecuch --- Created attachment 220667 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220667&action=edit tty: read s_leader exactly once in tty_signal_sessleader() -- You are receiving this mail because

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #3 from Konstantin Belousov --- (In reply to Jakub Piecuch from comment #2) One of the fundamental assumptions of the FreeBSD kernel code is that plain stores and loads of fundamental types (integers up to long and pointers) are

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #14 from commit-h...@freebsd.org --- A commit references this bug: Author: imp Date: Thu Dec 17 17:02:09 UTC 2020 New revision: 368721 URL: https://svnweb.freebsd.org/changeset/base/368721 Log: Drop EFI_STAGING_SIZE back down

[Bug 251918] strptime(): %b always returns month 0

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251918 Yuri Pankov changed: What|Removed |Added CC||yur...@freebsd.org Versio

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 --- Comment #2 from Jakub Piecuch --- (In reply to Konstantin Belousov from comment #1) I see. This should solve the problem, provided the compiler doesn't perform store tearing on any assignments to s_leader (which is a reasonable assumpti

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #13 from Andrew Turner --- It's early in the boot process. It looks like you can use /efi/freebsd/loader.env on the same fs as loader.efi (probably the FAT fs) to set early variables, e.g. to use the serial console. -- You are

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #12 from Dimitry Andric --- Would it print "Staging area's size is reduced:" before or after the initial messages? If it prints it very early, I cannot see it because the output scrolls off the screen, and the loader's prompt do

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #11 from Andrew Turner --- Did it print the line starting "Staging area's size is reduced:" and if so what did it print? -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #10 from YUAN RUI --- If (running_on_hyperv()) is commented out, this problem still occurs. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs

[Bug 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #10 from Jens Grassel --- Created attachment 220662 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220662&action=edit Output of dmesg Hi, here is the requested boot log (output of dmesg) after setting the debug.psm.

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #9 from Andrew Turner --- (In reply to Andrew Turner from comment #8) It looks like the issue is the first LoaderData memory. Can you try commenting out the if(running_on_hyperv()) check in efi_copy_init in copy.c so efi_verify_

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #8 from Andrew Turner --- It looks like the issue is the first LoaderData memory. Can you try commenting out the if(running_on_hyperv()) check in efi_copy_init in -- You are receiving this mail because: You are the assignee fo

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 --- Comment #7 from Dimitry Andric --- Note that this is with a loader.efi rebuilt with EFI_STAGING_SIZE=64: OK memmap Type Physical Virtual #Pages Attr ACPIMemoryNVS 00

[Bug 251727] [sound] [snd_hda] After update to r368166 no sound recording with internal microphone

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251727 --- Comment #10 from Matthias Apitz --- here is a proposal to fix this issue with values in device.hints(5) as: # grep init_clear /boot/device.hints hint.hdaa.0.init_clear=1 hint.hdaa.1.init_clear=1 # svn diff sys/dev/sound/pci/hda/hdaa.

[Bug 251866] Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 Andrew Turner changed: What|Removed |Added CC||and...@freebsd.org --- Comment #6

[Bug 251918] strptime(): %b always returns month 0

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251918 Bug ID: 251918 Summary: strptime(): %b always returns month 0 Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity:

[Bug 251868] Add tcgetwinsize() and tcsetwinsize() to termios.h

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251868 --- Comment #13 from SOUMENDRA GANGULY <0.gang...@gmail.com> --- The patches here are now outdated. New patches are on phabricator. -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 251915] TOCTOU race between tty_signal_sessleader() and killjobc()

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251915 Bug ID: 251915 Summary: TOCTOU race between tty_signal_sessleader() and killjobc() Product: Base System Version: CURRENT Hardware: Any OS: Any

[Bug 251727] [sound] [snd_hda] After update to r368166 no sound recording with internal microphone

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251727 --- Comment #9 from Andriy Gapon --- Sean, and I think that that was what I asked about here: https://reviews.freebsd.org/D17772#553549 sysctl.conf:dev.hdaa.0.init_clear=0 "worked" for you, because it seems that init_clear is always a zero

[Bug 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2

2020-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #9 from Vladimir Kondratyev --- (In reply to Jason W. Bacon from comment #6) > Just hit the same issue after upgrading an old MacBook Pro to 12.2. If your MacBook has a wsp(4) or an atp(4) touchpad, please open another one issue