[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521

--- Comment #294 from Henri Hennebert  ---
This morning I receive 320 Euro on my Paypal account.

Thank you to all donors and everyone for your help.

As planned, a donation of 295$ has been done to the FreeBSD Foundation.

-- 
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 248377] [PATCH] script(1): Enable proper playback [-p] of curses sessions

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248377

SOUMENDRA GANGULY <0.gang...@gmail.com> changed:

   What|Removed |Added

 Attachment #216900|script.diff |old.diff
description||

-- 
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 248377] [PATCH] script(1): Enable proper playback [-p] of curses sessions

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248377

SOUMENDRA GANGULY <0.gang...@gmail.com> changed:

   What|Removed |Added

 Attachment #216900|0   |1
is obsolete||
 CC||0.gang...@gmail.com

--- Comment #7 from SOUMENDRA GANGULY <0.gang...@gmail.com> ---
Created attachment 216951
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216951&action=edit
script.diff

This patch removes a lot of redundant code that was there in the old one.

-- 
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 248103] Multicast valid (vlan)interfaces do not get vif "Invalid phyint address"

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248103

--- Comment #5 from Louis  ---
I added a pfSence bootlog, showing what is started when. This shows in which
phase PIMD is started in conjunction with the start of the OS itself.

You can also see that PIMD is started (and stopped) multiple times. That is of
course not correct, however a pfSence issue

I attached this log since there is a possible relation between the PIMD start
behavior and the state of OS and interfaces at that particular moment.

It seems that interfaces needs to have an IP-assigned at the moment PIMD is
starting, which is probably the case (but something to check).

-- 
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 248103] Multicast valid (vlan)interfaces do not get vif "Invalid phyint address"

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248103

--- Comment #6 from Louis  ---
Created attachment 216957
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216957&action=edit
pfSense bootlog to show the pimd <> OS boot order

-- 
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"


Problem reports for b...@freebsd.org that need special attention

2020-08-02 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |197876 | [devfs] an error in devfs leads to data loss and  
New |198797 | [PATCH] Added an option to install BSDstats to bs 
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code   
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error 
Open|192573 | Add ps(1) option: Print process start time in sec 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C 
Open|207248 | [patch] daemon(8): Add option to redirect stdout  
Open|207940 | stand/efi/boot1: Add boot partition selection 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|222632 | connect(2) not available in capability mode   
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|237981 | cxgb(4): Driver doesn't work with latest (7.12) C 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|240572 | libefi: FreeBSD cannot boot with U-Boot patch efi 
Open|241697 | i915kms: Kernel panic loading module on custom ke 
Open|242212 | usr.sbin/mergemaster/mergemaster.sh: There is no  
Open|244181 | unzip: Add passphrase and GLIBC build support 
Open|244838 | "bectl activate -t" does not honor the -t flag in 
Open|247132 | Fix build error: use of undeclared identifier 'cp 
Open|247301 | linuxkpi: panic: Assertion td->td_lkpi_task == NU 
New |230955 | [patch] Some speedup mergemaster  

49 problems total for which you should take action.
___
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 248439] man page for ssh - authorized_keys2 no longer supported

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248439

Bug ID: 248439
   Summary: man page for ssh - authorized_keys2 no longer
supported
   Product: Base System
   Version: 12.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: d...@safeport.com

The openssh site says this was depreciated with version 3. In FreeBSD this
required for much longer. At lease by 12.0, OpenSSH_7.8p1, OpenSSL
1.1.1b-freebsd authorized_keys2 will not work. No error message is given.

man page: if this optionis not specified, the default is
 ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2. 

authorized_keys2 should be removed.

-- 
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 248439] man page for ssh - authorized_keys2 no longer supported

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248439

d...@safeport.com changed:

   What|Removed |Added

Version|12.0-STABLE |12.0-RELEASE

-- 
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 248440] kevent not returning full pipes registered with EVFILT_WRITE on read end closure

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248440

larkinc...@gmail.com changed:

   What|Removed |Added

Summary|kevent not returning full   |kevent not returning full
   |pipes registered with   |pipes registered with
   |EVFILT_WRITE when on read   |EVFILT_WRITE on read end
   |end closure |closure

-- 
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 248440] kevent not returning full pipes registered with EVFILT_WRITE when on read end closure

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248440

Bug ID: 248440
   Summary: kevent not returning full pipes registered with
EVFILT_WRITE when on read end closure
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: larkinc...@gmail.com
 Attachment #216970 text/plain
 mime type:

Created attachment 216970
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216970&action=edit
test program to reproduce bug via filling/monitoring stdout

When using kevent to monitor the write end of a pipe for writability via
EVFILT_WRITE, if the pipe is full when the read end is closed, an event is not
returned. I would expect an event with EV_EOF set to be returned. Note that
this does not seem to reproduce with sockets or named pipes (fifos), those
return an event with EV_EOF set just fine in this situation.

I'm attaching a sample program that verifies stdout is a pipe and then attempts
to fill  it with data, then waits for an event with EVFILT_WRITE for stdout. If
you pipe this to  some program that doesn't read stdin, for instance sleep(1),
the pipeline hangs forever. Notably, if you instead redirect its output to a
named pipe and have sleep "read" the named pipe with shell redirection, the
program *does* receive an event for stdout with EV_EOF set once sleep exits.

I originally detected this with a test case that creates a pipe via pipe(2) in
process, so testing with socketpair(2) was convenient, but it used threads and
other infrastructure etc so I wrote a new test program. But I just want to
mention that because it would seem to exclude some weird interaction with my
shell etc.

Example test case using the attached kqwrite.c:

$ ./kqwrite | /bin/sleep 1 # hangs forever
^C
$ mkfifo dummy; /bin/sleep 1 < dummy &; ./kqwrite > dummy # returns EV_EOF:
[1] 1734
kevent returned 1
1 -2 32768 0 0 0x0
[1]  + done   /bin/sleep 1 < dummy

-- 
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 31906] [libc] No method available to unwind atexit(3) stack without exiting

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=31906

Conrad Meyer  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events

-- 
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 248440] kqueue(2): kevent not returning full pipes registered with EVFILT_WRITE on read end closure

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248440

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
 CC||kev...@freebsd.org,
   ||ma...@freebsd.org
Summary|kevent not returning full   |kqueue(2): kevent not
   |pipes registered with   |returning full pipes
   |EVFILT_WRITE on read end|registered with
   |closure |EVFILT_WRITE on read end
   ||closure
   Severity|Affects Only Me |Affects Some People
  Flags||maintainer-feedback?(markj@
   ||FreeBSD.org)
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2033
   ||66,
   ||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2246
   ||15,
   ||https://reviews.freebsd.org
   ||/D24528
   Keywords||needs-qa

--- Comment #1 from Kubilay Kocak  ---
^Triage: Request feedback from markj per base r360380 base r360379 base
r360378, which may be related (or resolve) this issue.

@Mark If this is indeed resolved, could you please close this a duplicate of
the relevant issue ID (if this report matches a previously reported one)

-- 
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 224615] [PATCH] kevent: EVFILT_READ returns EV_EOF on named pipe when it should not

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224615

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2484
   ||40

-- 
You are receiving this mail because:
You are on the CC list 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 224615] kevent: EVFILT_READ returns EV_EOF on named pipe when it should not

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224615

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||mfc-stable12+
Summary|[PATCH] kevent: EVFILT_READ |kevent: EVFILT_READ returns
   |returns EV_EOF on named |EV_EOF on named pipe when
   |pipe when it should not |it should not

-- 
You are receiving this mail because:
You are on the CC list 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 248441] drm-kmod dump core

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248441

Bug ID: 248441
   Summary: drm-kmod dump core
   Product: Base System
   Version: 11.4-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: gh_ori...@yahoo.com

Forum thread: https://forums.freebsd.org/threads/drm-kmod-dump-core.76216/

If you need the content under /var/crash, and if they don't contain sensitive
information (like my passwords) I will upload it.

-- 
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 248441] graphics/drm-kmod:drm-kmod dump core

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248441

Kubilay Kocak  changed:

   What|Removed |Added

Product|Base System |Ports & Packages
  Flags||maintainer-feedback?(x11@Fr
   ||eeBSD.org)
Version|11.4-RELEASE|Latest
  Component|kern|Individual Port(s)
URL||https://forums.freebsd.org/
   ||threads/drm-kmod-dump-core.
   ||76216/
 Status|New |Open
   Keywords||crash, needs-qa
 CC||x...@freebsd.org
   Assignee|b...@freebsd.org|ports-b...@freebsd.org
Summary|drm-kmod dump core  |graphics/drm-kmod:drm-kmod
   ||dump core

--- Comment #1 from Kubilay Kocak  ---
Thank you for your report. Can you please include additional information,
including:

- uname -a output
- /var/run/dmesg.boot output (as an attachment)
- pciconf -lv output (as an attachment)
- pkg version -v output (as an attachment)
- /boot/loader.conf output (as an attachment)
- Backtrace (ideally) or screenshot of the crash/panic

-- 
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 243807] CURRENT libedit breaks emacs tramp-mode

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243807

--- Comment #11 from Yuichiro NAITO  ---
emacs@
Could you please apply 'emacs-port.patch' to Ports tree?

I talked about this PR in FreeBSD workshop Tokyo on July 31.
The organizer hrs@ said that he wants to use this patch on FreeBSD Ports.

-- 
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 248377] [PATCH] script(1): Enable proper playback [-p] of curses sessions

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248377

SOUMENDRA GANGULY <0.gang...@gmail.com> changed:

   What|Removed |Added

 Attachment #216951|0   |1
is obsolete||

--- Comment #8 from SOUMENDRA GANGULY <0.gang...@gmail.com> ---
Created attachment 216973
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216973&action=edit
script.diff

Removes unnecessary "ttyflg = 0" at the beginning of playback() in previous
patch because static global variable ttyflg will automatically be initialized
to 0 by compiler.

-- 
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 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442

Bug ID: 248442
   Summary: [Hyper-V] ng_vlan on hn interface not forwarding
packets
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: reshadpatu...@gmail.com

Created attachment 216974
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216974&action=edit
Script to create a base jail on a FreeBSD 12.1 VM

I am trying to use ng_vlan on Hyper-V to deploy vnet jails.
The "Enable MAC address Spoofing" setting on the Hyper-V host is enabled.
However when I try to use ng_vlan I am not able to reach the jail.
If I change this to if_vlan instead everything works fine.

Here are the symptoms for an ng_vlan jail with a static IP when I try to ping
it.
- The arp request from the gateway is visible on hn1, the vlan interface
(hn1vl50), the bridge interface (hn1vl50br) and the epair interface inside the
jail.
- The outbound arp response is visible on the same interfaces
- Wireshark on the interface with the trunked vlans on windows (Ethernet 1)
does not see any ARP response (I can see the requests)
- The gateway does not see the arp response and continues to send arp requests
for the IP

Is there something that creating a VLAN using ifconfig does to the interface
that ng_vlan does not?
The same setup works well on VMware ESXi, Xen and KVM.

I am not sure if this is relevant to my issue but the hn1 devices sysrc's
changes when I use different methods to set vlans on bsd:

no vlan:
dev.hn.1.rxfilter: 9
dev.hn.1.hwassist: 17

if_vlan:
dev.hn.1.rxfilter: 20
dev.hn.1.hwassist: 17

ng_vlan:
dev.hn.1.rxfilter: 9
dev.hn.1.hwassist: 0

All the other sysrc's either stay the same or seem to be counters.

I have attached:
- A shell script to setup everything from a default zfs install of FreeBSD 12.1
- The powershell commands I use to setup VLANs on Hyper-V
- A shell script to setup vnet jails using both ng_vlan and if_vlan on a
Hyper-V VM with 2 hn interfaces.

Any help understanding what these sysrc's do, and on how I could get ng_vlan to
work would be very appreciated.

I have tested this on Hyper-V on Windows Server 2012 R2 and Windows Server
2016.

-- 
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 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442

Reshad Patuck  changed:

   What|Removed |Added

   Hardware|Any |amd64

-- 
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 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442

--- Comment #1 from Reshad Patuck  ---
Created attachment 216975
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216975&action=edit
PowerShell commands to set Hyper-V to trunk VLANs

-- 
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 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442

--- Comment #2 from Reshad Patuck  ---
Created attachment 216976
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216976&action=edit
Shell script to create if_vlan interface and jail on the VLAN

This script works, The jail can connect out and systems can connect to the jail

-- 
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 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442

--- Comment #3 from Reshad Patuck  ---
Created attachment 216977
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216977&action=edit
Shell script to create ng_vlan interface and jail on the VLAN

This scrpt does not work, the jail can not connect our nor can an external
system connect to the jail.

-- 
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 248443] Panic on jail to host TCP transmission

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248443

Bug ID: 248443
   Summary: Panic on jail to host TCP transmission
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: pom...@typeof.pw

'mysqld' issued a system call that panicked the kernel.

kernel: Fatal trap 12: page fault while in kernel mode
kernel: cpuid = 0; apic id = 00
kernel: fault virtual address = 0x18
kernel: fault code= supervisor read data, page not present
kernel: instruction pointer   = 0x20:0x80c5d6f0
kernel: stack pointer = 0x28:0xfe001139e4b0
kernel: frame pointer = 0x28:0xfe001139e4e0
kernel: code segment  = base 0x0, limit 0xf, type 0x1b
kernel:   = DPL 0, pres 1, long 1, def32 0, gran 1
kernel: processor eflags  = interrupt enabled, resume, IOPL = 0
kernel: current process   = 98556 (mysqld)
kernel: trap number   = 12
kernel: panic: page fault
kernel: cpuid = 0
kernel: time = 1596433787
kernel: KDB: stack backtrace:
kernel: #0 0x80c1d2f7 at kdb_backtrace+0x67
kernel: #1 0x80bd062d at vpanic+0x19d
kernel: #2 0x80bd0483 at panic+0x43
kernel: #3 0x810a8dcc at trap_fatal+0x39c
kernel: #4 0x810a8e19 at trap_pfault+0x49
kernel: #5 0x810a840f at trap+0x29f
kernel: #6 0x81081c9c at calltrap+0x8
kernel: #7 0x80ded2a2 at tcp_output+0x1232
kernel: #8 0x80dff2ca at tcp_usr_send+0x47a
kernel: #9 0x80c68d7a at sosend_generic+0x51a
kernel: #10 0x80c69160 at sosend+0x50
kernel: #11 0x80c6ffd7 at kern_sendit+0x237
kernel: #12 0x80c7034e at sendit+0x19e
kernel: #13 0x80c7019d at sys_sendto+0x4d
kernel: #14 0x810a9984 at amd64_syscall+0x364
kernel: Fatal trap 12: page fault while in kernel mode
kernel: cpuid = 0; apic id = 00
kernel: fault virtual address = 0x18
kernel: fault code= supervisor read data, page not present
kernel: instruction pointer   = 0x20:0x80c5d6f0
kernel: stack pointer = 0x28:0xfe001139e4b0
kernel: frame pointer = 0x28:0xfe001139e4e0
kernel: code segment  = base 0x0, limit 0xf, type 0x1b
kernel:   = DPL 0, pres 1, long 1, def32 0, gran 1
kernel: processor eflags  = interrupt enabled, resume, IOPL = 0
kernel: current process   = 98556 (mysqld)
kernel: trap number   = 12
kernel: panic: page fault
kernel: cpuid = 0
kernel: time = 1596433787
kernel: KDB: stack backtrace:
kernel: #0 0x80c1d2f7 at kdb_backtrace+0x67
kernel: #1 0x80bd062d at vpanic+0x19d
kernel: #2 0x80bd0483 at panic+0x43
kernel: #3 0x810a8dcc at trap_fatal+0x39c
kernel: #4 0x810a8e19 at trap_pfault+0x49
kernel: #5 0x810a840f at trap+0x29f
kernel: #6 0x81081c9c at calltrap+0x8
kernel: #7 0x80ded2a2 at tcp_output+0x1232
kernel: #8 0x80dff2ca at tcp_usr_send+0x47a
kernel: #9 0x80c68d7a at sosend_generic+0x51a
kernel: #10 0x80c69160 at sosend+0x50
kernel: #11 0x80c6ffd7 at kern_sendit+0x237
kernel: #12 0x80c7034e at sendit+0x19e
kernel: #13 0x80c7019d at sys_sendto+0x4d
kernel: #14 0x810a9984 at amd64_syscall+0x364
kernel: KDB: stack backtrace:
kernel: #0 0x80c1d2f7 at kdb_backtrace+0x67
kernel: #1 0x80bd062d at vpanic+0x19d
kernel: #2 0x80bd0483 at panic+0x43
kernel: #3 0x80ee8b92 at ffs_bufwrite+0x352
kernel: #4 0x80c815fc at vfs_bio_awrite+0x36c
kernel: #5 0x80cb4982 at vn_fsync_buf+0x262
kernel: #6 0x8122ba0c at VOP_FSYNC_APV+0x7c
kernel: #7 0x80ee808d at ffs_sync+0x32d
kernel: #8 0x80ca793e at sys_sync+0x11e
kernel: #9 0x80c7f581 at bufshutdown+0x31
kernel: #10 0x80bcffd2 at kern_reboot+0x212
kernel: #11 0x80bd0689 at vpanic+0x1f9
kernel: #12 0x80bd0483 at panic+0x43
kernel: #13 0x810a8dcc at trap_fatal+0x39c
kernel: #14 0x810a8e19 at trap_pfault+0x49
kernel: #15 0x810a840f at trap+0x29f
kernel: #16 0x81081c9c at calltrap+0x8
kernel: #17 0x80ded2a2 at tcp_output+0x1232
kernel: Uptime: 42m6s
kernel: Rebooting...

-- 
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 248444] /usr/sbin/jail crashes when parsing certain configuration files

2020-08-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248444

Bug ID: 248444
   Summary: /usr/sbin/jail crashes when parsing certain
configuration files
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: ms-freebsd-bugzi...@stoffnet.at
CC: ms-freebsd-bugzi...@stoffnet.at

Some variable names may cause the configuration parser to crash. So far I could
only reproduce this issue with "$interface".

Example:

Setting "$interface" in two jail configurations ("crash" and "nocrash"). Using
any jail configuration but the last one ("nocrash") will crash the
configuration parser. You could have any number of crashing jails ("crash1",
"crash2", ...), but only one jail that does not crash (the bottom most one).

jail.conf:

persist;
exec.prestart = "echo '\$interface = ${interface}'";

crash {
$interface = "vr0";
}

nocrash {
$interface = "vr1";
}

How to reproduce:

# jail -f jail.conf -c crash
Segmentation fault (core dumped)

# jail -f crash.conf -c nocrash
$interface = vr1
nocrash: created
# jail -f crash.conf -r nocrash
nocrash: removed

-- 
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"