[Bug 224336] /etc/pkg/FreeBSD.conf should use HTTPS by default

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224336

--- Comment #6 from Baptiste Daroussin  ---
Again from what has been said above, Can you state what is insecure in the
process, given the signatures?

-- 
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 210686] NCQ_TRIM_BROKEN quirk mismatch

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210686

Vladimir  changed:

   What|Removed |Added

 CC||w0w...@gmail.com

--- Comment #10 from Vladimir  ---
 Tomoaki AOKI, is there workaround without patching the system? I saw something
you have posted about loader.conf need 1 line to be added, but you did not
provide  information of what exactly it should be. Thanks.

-- 
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 224426] fetch -i runs in an endless loop

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224426

Bug ID: 224426
   Summary: fetch -i runs in an endless loop
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: wo...@freebsd.org

I wanted to try out the -i option of the fetch(1) command for the build of our
website.

 -i file, --if-modified-since=file
 If-Modified-Since mode: the remote file will only be
 retrieved if it is newer than file on the local host.  (HTTP
 only)

I also had the -a option in use. I run into an endless loop.

how to repeat:

# first run, file is not up-to-date
$ touch index.html
$ time fetch -a -o index.html -i index.html https://www.FreeBSD.org 

real0m0.887s
user0m0.019s
sys 0m0.016s

# second run, file is up-to-date
$ time fetch -a -o index.html -i index.html https://www.FreeBSD.org
time fetch -a -o index.html -i index.html https://www.FreeBSD.org 
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
fetch: https://www.FreeBSD.org: Not Modified
^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 218452] I can cause an assertion with a dtrace script and when it does happen, dtrace fails until the module dtraceall is reloaded

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218452

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

Author: markj
Date: Mon Dec 18 17:26:25 UTC 2017
New revision: 326935
URL: https://svnweb.freebsd.org/changeset/base/326935

Log:
  Avoid CPU migration in dtrace_gethrtime() on x86.

  dtrace_gethrtime() may be called outside of probe context, and in
  particular, from the DTRACEIOC_BUFSNAP handler.

  Disable interrupts rather than using sched_pin() to help ensure that
  we don't call any external functions when in probe context.

  PR:   218452
  MFC after:1 week

Changes:
  head/sys/cddl/dev/dtrace/amd64/dtrace_subr.c
  head/sys/cddl/dev/dtrace/i386/dtrace_subr.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 218452] I can cause an assertion with a dtrace script and when it does happen, dtrace fails until the module dtraceall is reloaded

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218452

Mark Johnston  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|ma...@freebsd.org

--- Comment #10 from Mark Johnston  ---
I haven't been able to reproduce this in bhyve, but would be interested in
knowing whether it still occurs after r326935.

-- 
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 224433] `make buildkernel' should display the build time in seconds

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224433

Bug ID: 224433
   Summary: `make buildkernel' should display the build time in
seconds
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: wo...@freebsd.org

When I run `make buildkernel' the makefile display the start end completed
time:

>>> Kernel build for GENERIC started on Sun Dec 17 20:37:08 UTC 2017
[...]
>>> Kernel build for GENERIC completed on Sun Dec 17 20:39:14 UTC 2017

but wouldn't it be great if the makefile display the build time in seconds? 

E.g.:

>>> Kernel build for GENERIC in 125 seconds, ncpu: 32, make -j27
(incl. number of CPUs and the make -j flags)

-- 
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 224433] `make buildkernel' should display the build time in seconds

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224433

--- Comment #1 from Wolfram Schneider  ---
Created attachment 188938
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188938&action=edit
makefile patch

-- 
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 222987] ARM64 panic in iflib.c:2944

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222987

--- Comment #2 from Antoine Brodin  ---
Another panic from yesterday:

KDB: reentering
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+40
 pc = 0x005e72e8  lr = 0x00086ad4
 sp = 0x000b96c21810  fp = 0x000b96c21a20

db_trace_self_wrapper() at kdb_reenter+56
 pc = 0x00086ad4  lr = 0x00350a2c
 sp = 0x000b96c21a30  fp = 0x000b96c21a40

kdb_reenter() at db_term+260
 pc = 0x00350a2c  lr = 0x00085764
 sp = 0x000b96c21a50  fp = 0x000b96c21a60

db_term() at db_mult_expr+40
 pc = 0x00085764  lr = 0x000853dc
 sp = 0x000b96c21a70  fp = 0x000b96c21ad0

db_mult_expr() at db_add_expr+40
 pc = 0x000853dc  lr = 0x000852d0
 sp = 0x000b96c21ae0  fp = 0x000b96c21b40

db_add_expr() at db_shift_expr+36
 pc = 0x000852d0  lr = 0x000851cc
 sp = 0x000b96c21b50  fp = 0x000b96c21ba0

db_shift_expr() at db_logical_relation_expr+40
 pc = 0x000851cc  lr = 0x00085058
 sp = 0x000b96c21bb0  fp = 0x000b96c21c10

db_logical_relation_expr() at db_logical_and_expr+28
 pc = 0x00085058  lr = 0x00084f98
 sp = 0x000b96c21c20  fp = 0x000b96c21c50

db_logical_and_expr() at db_expression+28
 pc = 0x00084f98  lr = 0x00084eec
 sp = 0x000b96c21c60  fp = 0x000b96c21c90

db_expression() at db_stack_trace+44
 pc = 0x00084eec  lr = 0x00084044
 sp = 0x000b96c21ca0  fp = 0x000b96c21cd0

db_stack_trace() at db_command+548
 pc = 0x00084044  lr = 0x00083d90
 sp = 0x000b96c21ce0  fp = 0x000b96c21dc0

db_command() at db_command_loop+96
 pc = 0x00083d90  lr = 0x00083b50
 sp = 0x000b96c21dd0  fp = 0x000b96c21df0

db_command_loop() at db_trap+244
 pc = 0x00083b50  lr = 0x00086c3c
 sp = 0x000b96c21e00  fp = 0x000b96c22020

db_trap() at kdb_trap+400
 pc = 0x00086c3c  lr = 0x00350e18
 sp = 0x000b96c22030  fp = 0x000b96c22090

kdb_trap() at do_el1h_sync+144
 pc = 0x00350e18  lr = 0x00600adc
 sp = 0x000b96c220a0  fp = 0x000b96c220d0

do_el1h_sync() at handle_el1h_sync+116
 pc = 0x00600adc  lr = 0x005e9074
 sp = 0x000b96c220e0  fp = 0x000b96c221f0

handle_el1h_sync() at kdb_enter+52
 pc = 0x005e9074  lr = 0x00350520
 sp = 0x000b96c22200  fp = 0x000b96c22290

kdb_enter() at vpanic+416
 pc = 0x00350520  lr = 0x00311638
 sp = 0x000b96c222a0  fp = 0x000b96c22320

vpanic() at panic+68
 pc = 0x00311638  lr = 0x003116a4
 sp = 0x000b96c22330  fp = 0x000b96c223b0

panic() at data_abort+592
 pc = 0x003116a4  lr = 0x00600e98
 sp = 0x000b96c223c0  fp = 0x000b96c22470

data_abort() at do_el1h_sync+248
 pc = 0x00600e98  lr = 0x00600b44
 sp = 0x000b96c22480  fp = 0x000b96c224b0

do_el1h_sync() at handle_el1h_sync+116
 pc = 0x00600b44  lr = 0x005e9074
 sp = 0x000b96c224c0  fp = 0x000b96c225d0

handle_el1h_sync() at _iflib_fl_refill+880
 pc = 0x005e9074  lr = 0x00410844
 sp = 0x000b96c225e0  fp = 0x000b96c226d0

_iflib_fl_refill() at _iflib_fl_refill+880
 pc = 0x00410844  lr = 0x00410844
 sp = 0x000b96c226e0  fp = 0x000b96c227a0

_iflib_fl_refill() at iflib_init_locked+992
 pc = 0x00410844  lr = 0x0040c5d4
 sp = 0x000b96c227b0  fp = 0x000b96c22810

iflib_init_locked() at _task_fn_admin+460
 pc = 0x0040c5d4  lr = 0x0040b3f8
 sp = 0x000b96c22820  fp = 0x000b96c22860

_task_fn_admin() at gtaskqueue_run_locked+264
 pc = 0x0040b3f8  lr = 0x0034f14c
 sp = 0x000b96c22870  fp = 0x000b96c228e0

gtaskqueue_run_locked() at gtaskqueue_thread_loop+156
 pc = 0x0034f14c  lr = 0x0034eee4
 sp = 0x000b96c228f0  fp = 0x000b96c22910

gtaskqueue_thread_loop() at fork_exit+124
 pc = 0x0034eee4  lr = 0x002d661c
 sp = 0x000b96c22920  fp = 0x000b96c22950

fork_exit() at fork_trampoline+16
 pc = 0x002d661c  lr = 0x006008bc
 sp = 0x000b96c22960  fp = 0x

-- 
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/f

[Bug 224433] `make buildkernel' should display the build time in seconds

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224433

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #2 from Ed Maste  ---
Comment on attachment 188938
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188938
makefile patch

Shouldn't buildworld get the same treatment?

-- 
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 224433] `make buildkernel' should display the build time in seconds

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224433

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
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 224436] vt: CONS_CLRHIST (vidcontrol -C) not implemented

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224436

Bug ID: 224436
   Summary: vt: CONS_CLRHIST (vidcontrol -C) not implemented
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: vt
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ema...@freebsd.org
 Flags: mfc-stable9-, mfc-stable10-, mfc-stable11?

Steps to reproduce:
% vidcontrol -C

Expected behaviour:
Scrollback cleared (e.g. confirm with ScrLk / PgUp)

Observed behaviour:
% vidcontrol -C
vidcontrol: clearing history buffer: Inappropriate ioctl for device

-- 
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 224436] vt: CONS_CLRHIST (vidcontrol -C) not implemented

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224436

Ed Maste  changed:

   What|Removed |Added

 Blocks||203349


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349
[Bug 203349] [META] FreeBSD Foundation sponsored project dependencies for
FreeBSD 11.x
-- 
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 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.x

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349

Ed Maste  changed:

   What|Removed |Added

 Depends on||224436


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224436
[Bug 224436] vt: CONS_CLRHIST (vidcontrol -C) not implemented
-- 
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 213497] Vidcontrol is a complete disaster!

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213497

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #2 from Ed Maste  ---
(In reply to nibbana from comment #1)
I can't reproduce the lynx problem. What is your environment? (UEFI vs BIOS,
video hw, etc.)

-- 
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 224437] [PATCH] powerpc64: Fix cookie verification on boot

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224437

Bug ID: 224437
   Summary: [PATCH] powerpc64: Fix cookie verification on boot
   Product: Base System
   Version: CURRENT
  Hardware: powerpc
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: grom...@br.ibm.com
  Keywords: patch

Created attachment 188943
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188943&action=edit
Patch for this bug

Currently kernel fails to boot on PPC64 because the cookie value
passed to kernel by the loader and which should be regarded as a 32-bit
value is promoted on 64-bit machines to unsigned long (aka vm_offset_t)
and thus results in 0xfb5d104d instead of 0xfb5d104d. That
causes kernels to fail booting even if the loader is update to the most
recent one by the user, i.e. user falls into "mountroot>" prompt and
has to pass again the boot device to continue to boot process.

So after a new kernel updated boot shows:

Loader variables:

Manual root filesystem specification:
  : [options]
  Mount  using filesystem 
  and with the specified (optional) option list.

eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/cd0 ro
  (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

  ?   List valid disk boot devices
  .   Yield 1 second (for background tasks)
  Abort manual input

mountroot> 


That commit fixes that issue by ensuring that the cookie passed from loader
to kernel is a 32-bit unsigned value both on PPC32 and PPC64 machines.

-- 
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 224437] [PATCH] powerpc64: Fix cookie verification on boot

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224437

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@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 224300] sys/sem.h improperly declares union semun

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224300

--- Comment #2 from Brooks Davis  ---
That would be a reasonable approach.  In the patch I'm working on for an
exp-run I've simply redeclared 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 224443] exp-run: SysV IPC API cleanup

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443

Bug ID: 224443
   Summary: exp-run: SysV IPC API cleanup
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: bro...@freebsd.org
Blocks: 224299, 224300

The System V message queue and semaphore headers and APIs contain a number of
mistakes.   Some types are declared that should not be, and the *id_ds structs
contain kernel-only members.

The review https://reviews.freebsd.org/D13538 contains a patch which removes
the types that should not be declared, fixes the system as required, and
renames the kernel-only, non-standard members to break existing consumers (if
any).  This isn't expected to break much as standard autoconf macros exist to
detect the most common issue (improperly declaring union semun).  The *is_ds
member changes are to explore the possibility of revising the APIs to remove
the members.


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224299
[Bug 224299] sys/msg.h improperly declares struct mymsg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224300
[Bug 224300] sys/sem.h improperly declares union semun
-- 
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 224300] sys/sem.h improperly declares union semun

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224300

Brooks Davis  changed:

   What|Removed |Added

 Depends on||224443


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443
[Bug 224443] exp-run: SysV IPC API cleanup
-- 
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 224299] sys/msg.h improperly declares struct mymsg

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224299

Brooks Davis  changed:

   What|Removed |Added

 Depends on||224443


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443
[Bug 224443] exp-run: SysV IPC API cleanup
-- 
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 224443] exp-run: SysV IPC API cleanup

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443

--- Comment #1 from Brooks Davis  ---
Created attachment 188945
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188945&action=edit
Patch revising SysV IPAPIs

-- 
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 224443] exp-run: SysV IPC API cleanup

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443

Brooks Davis  changed:

   What|Removed |Added

  Flags||exp-run?

-- 
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 224443] exp-run: SysV IPC API cleanup

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443

Brooks Davis  changed:

   What|Removed |Added

 Attachment #188945|Patch revising SysV IPAPIs  |Patch revising SysV IPC
description||APIs

-- 
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 224443] exp-run: SysV IPC API cleanup

2017-12-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224443

Antoine Brodin  changed:

   What|Removed |Added

 CC||freebsd-ports-bugs@FreeBSD.
   ||org
Version|CURRENT |Latest
Product|Base System |Ports & Packages
   Assignee|freebsd-bugs@FreeBSD.org|port...@freebsd.org
  Component|kern|Ports Framework

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