1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
|
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
Status Report//EN"
"http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
<!-- $FreeBSD$ -->
<!--
Variables to replace:
01 - report month start
03 - report month end
2020 - report year
%%NUM%% - report issue (first, second, third, fourth)
%%STARTNEXT%% - report month start
%%STOPNEXT%% - report month end
%%YEARNEXT%% - next report due year (if different than 2020)
%%DUENEXT%% - next report due date (i.e., June 6)
-->
<report>
<date>
<month>01-03</month>
<year>2020</year>
</date>
<section>
<title>Introduction</title>
<p>Welcome, to the quarterly reports, of the future! Well, at least the first
quarterly report from 2020. The new timeline, mentioned in the last few
reports, still holds, which brings us to this report, which covers the period
of January 2020 - March 2020.
</p>
<p>As you will see from this report, we've had quite an active quarter with big
changes to both kernel, userland, documentation, ports, and third-party
projects in the form of everything from bug and security fixes over new features
to speed improvements and optimizations.
</p>
<p>As this report also covers the start of the epidemic, it's also interesting to
note that a quick glance at the svn logs reveal that there has been no overall
drop in number of source commits, that docs commits have also stayed constant,
and that ports have seen an upwards trend.
</p>
<p>We hope that all of you are and yours are as safe as can be managed, and that
we get through this together by working together.
</p>
<p>-- Daniel Ebdrup Jensen, <a href='mailto:debdrup@freebsd.org'>debdrup@freebsd.org</a>
</p> </section>
<project cat='team'>
<title>FreeBSD Foundation</title>
<contact>
<person>
<name>Deb Goodkin</name>
<email>deb@FreeBSDFoundation.org</email>
</person>
</contact>
<body><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
supporting and promoting the FreeBSD Project and community worldwide. Funding
comes from individual and corporate donations and is used to fund and manage
software development projects, conferences and developer summits, and provide
travel grants to FreeBSD contributors. The Foundation purchases and supports
hardware to improve and maintain FreeBSD infrastructure and provides resources
to improve security, quality assurance, and release engineering efforts;
publishes marketing material to promote, educate, and advocate for the FreeBSD
Project; facilitates collaboration between commercial vendors and FreeBSD
developers; and finally, represents the FreeBSD Project in executing contracts,
license agreements, and other legal arrangements that require a recognized
legal entity.
</p>
<p>Here are some highlights of what we did to help FreeBSD last quarter:
</p>
<h3>General</h3>
<p>We moved! Our new address is:<br />
The FreeBSD Foundation<br />
3980 Broadway St. STE #103-107<br />
Boulder, CO 80304<br />
USA<br />
</p>
<p>In February, the board of directors had an all-day board meeting in Berkely, CA,
where FreeBSD began! We put together our strategic plans for the next 2 years,
which includes software developments projects we want to support and some
educational initiatives.
</p>
<p>COVID-19 impacts the Foundation. We put policies in place for all of our staff
members to work from home. We also put a temporary ban on travel for staff
members. We are continuing our work supporting the community and Project, but
some of our work and responses are delayed because of changes in some of our
priorities and the impact of limited childcare for a few of our staff members.
</p>
<h3>Partnerships and Commercial User Support</h3>
<p>We help facilitate collaboration between commercial users and FreeBSD
developers. We also meet with companies to discuss their needs and bring that
information back to the Project. In Q1, Deb Goodkin met with commercial users
at LinuxConfAu in Australia, FOSDEM in Belgium, and SCALE18x in the US. These
venues provide an excellent opportunity to meet with commercial and individual
users and contributors to FreeBSD. It's not only beneficial for the above, but
it also helps us understand some of the applications where FreeBSD is used.
In addition to meeting with commercial users at conferences, we continued
discussions over email or on calls over the quarter.
</p>
<h3>Fundraising Efforts</h3>
<p>Last quarter we raised $57,000! Thank you to everyone who came through,
especially in this economic crisis we have found ourselves in. It heartens us
deeply that individuals and organizations have supported our efforts, when there
are so many people, animals, and businesses in need right now. We also want to
extend a big thank you to Tarsnap, VMWare, and Stormshield for leading the way
with Silver level donations. We hope other organizations will follow their lead
and give back to help us continue supporting FreeBSD.
</p>
<p>We are 100% funded by donations, and those funds go towards software development
work to improve FreeBSD, FreeBSD advocacy around the world, keeping FreeBSD
secure, continuous integration improvements, sponsoring BSD-related and
computing conferences, legal support for the Project, and many other areas.
</p>
<p>Please consider making a donation to help us continue and increase our support
for FreeBSD: https://www.FreeBSDfoundation.org/donate/.
</p>
<p>We also have the Partnership Program, to provide more benefits for our larger
commercial donors. Find out more information at
https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ and
share with your companies!
</p>
<h3>OS Improvements</h3>
<p>The Foundation supports software development projects to improve the FreeBSD
operating system through our full time technical staff, contractors, and project
grant recipients. They maintain and improve critical kernel subsystems, add new
features and functionality, and fix problems.
</p>
<p>Over the last quarter there were 273 commits to the FreeBSD base system source
repository tagged with FreeBSD Foundation sponsorship, about 12% of base system
commits over the quarter. Many of these are part of sponsored or staff projects
that have their own entries in this FreeBSD Quarterly Report, but Foundation
staff and contractors (Ed Maste, Konstantin Belousov, Mark Johnston, Li-Wen Hsu)
also support the project with an ongoing series of bug fixes, build fixes, and
miscellaneous improvements that don't warrant a separate entry.
</p>
<p>Ed committed miscellaneous improvements to various parts of FreeBSD's build
infrastructure, largely prompted by the work to retire the obsolete GCC 4.2.1.
This included removal of the <i>LLVM_LIBUNWIND</i> option (now always set), and
the removal of unused gperf, gcov, and the GPL devicetree compiler (dtc). Ed
committed sendfile support for the Linuxulator, submitted by previous intern
Bora Özarslan, and tested and committed a number of submitted bug fixes for
the Microchip USB-Ethernet controller <i>if_muge</i> driver. Ed also updated the
copy of OpenSSH in the base system to 7.9p1, with additional updates in
progress, and worked on a number of security advisories released during the
quarter.
</p>
<p>Konstantin Belousov and Mark Johnston both performed a large number of code
reviews during the quarter under Foundation sponsorship. This work helps
developers in the FreeBSD community and those working at companies using
FreeBSD to integrate their work into FreeBSD.
</p>
<p>In addition to work described elsewhere in this report Konstantin also
continued his usual series of bug fixes and improvements. This quarter this
included low-level x86 support, fixing sendfile bugs, file system and vfs
bug fixes, and dozens of other miscellaneous improvements. Additional work
included a variety of commits to support Hygon x86 CPUs and improvements to
the runtime linker (rtld)'s direct execution mode.
</p>
<p>Mark Johnston continued his work on the
<a href='https://syzkaller.appspot.com/freebsd'>Syzkaller</a> system-call fuzzer, and
committed fixes for many issues reported by Syzkaller. Mark triaged a large
number of submitted bug reports and in many cases committed attached patches
or developed fixes. Mark also addressed dozens of Coverity Scan reports.
</p>
<p>Mark's other changes included arm64 Large System Extensions (LSE) atomic
operations, low-level arm64 and x86 work, virtual memory (VM) work, and bug
fixes or other improvements to syslog, the lagg(4) link aggregation driver,
and build reproducibility.
</p>
<p>Li-Wen Hsu committed many changes to tests in the base system, such as turning
off known failing tests tracked by PRs, test-related pkgbase fixes, and other
improvements.
</p>
<h3>Continuous Integration and Quality Assurance</h3>
<p>The Foundation provides a full-time staff member who is working on improving
our automated testing, continuous integration, and overall quality assurance
efforts.
</p>
<p>During the first quarter of 2020, Foundation staff continued to improve the
Project's CI infrastructure, worked with contributors to fix the failing build
and test cases. The building of a CI staging environment is in progress on the
new machine purchased by the Foundation. We are also working with other teams
in the Project for their testing needs. For example, we added a new job for
running LTP (Linux Testing Project) on the Linuxulator, to validate improvements
in the Foundation's sponsored Linux emulation work. We are also working with
many external projects and companies to improve their support of FreeBSD.
</p>
<p>See the FreeBSD CI section of this report for completed work items and detailed
information.
</p>
<h3>Supporting FreeBSD Infrastructure</h3>
<p>The Foundation provides hardware and support to improve the FreeBSD
infrastructure. Last quarter, we continued supporting FreeBSD hardware located
around the world. We purchased one server for a mirror in Malaysia, and signed
the MOU for the new NYI colocation facility in Illinois. NYI generously
provides this as an in-kind donation to the Project.
</p>
<h3>FreeBSD Advocacy and Education</h3>
<p>A large part of our efforts are dedicated to advocating for the Project. This
includes promoting work being done by others with FreeBSD; producing advocacy
literature to teach people about FreeBSD and help make the path to starting
using FreeBSD or contributing to the Project easier; and attending and getting
other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
tables, and give FreeBSD presentations.
</p>
<p>The FreeBSD Foundation sponsors many conferences, events, and summits around the
globe. These events can be BSD-related, open source, or technology events
geared towards underrepresented groups. We support the FreeBSD-focused events
to help provide a venue for sharing knowledge, to work together on projects, and
to facilitate collaboration between developers and commercial users. This all
helps provide a healthy ecosystem. We support the non-FreeBSD events to promote
and raise awareness of FreeBSD, to increase the use of FreeBSD in different
applications, and to recruit more contributors to the Project.
</p>
<p>Check out some of the advocacy and education work we did last quarter:
</p>
<ul>
<li><p>Organized and presented at the first ever FreeBSD Mini-Conf LinuxConfAu 2020,
in Gold Coast, Australia in addition to sponsoring the conference itself.
<a href='https://www.freebsdfoundation.org/blog/freebsd-miniconf-at-lca2020-conference-recap/'>The recap can be found here</a>.
</p>
</li>
<li><p>Presented BSD Dev Room at FOSDEM '20, in Brussels, Belgium and represented
FreeBSD at a stand along with other members of the community. [Find out more
here](https://www.freebsdfoundation.org/blog/fosdem-2020-conference-recap/).
</p>
</li>
<li><p>Represented FreeBSD at Apricot 2020 in Melbourne, Australia and sponsored the
event.
</p>
</li>
<li><p>Industry Partner Sponsor for USENIX FAST '20 in Santa Clara, CA
</p>
</li>
<li><p>Sponsored FOSSASIA 2020, in Singapore
</p>
</li>
<li><p>Committed to hold FreeBSD Day at SCALE 18x, in Pasadena, CA
</p>
</li>
<li><p>Held a "Getting Started with FreeBSD Workshop" at SCALE 18x in addition to
giving a talk, representing FreeBSD at the Expo and holding a "Why FreeBSD is
Me" BoF. Check out the <a href='https://www.freebsdfoundation.org/blog/scale-18x-conference-recap/'>conference recap</a>.
</p>
</li></ul>
We continued producing FreeBSD advocacy material to help people promote FreeBSD.
<p>Learn more about our efforts in 2019 to <a href='https://www.freebsdfoundation.org/blog/2019-in-review-advocacy/'>advocate for FreeBSD</a>.
</p>
<p>In addition to the information found in the Development Projects update section
of this report, take a minute to check out the latest update blogs:
</p>
<ul>
<li><p><a href='https://www.freebsdfoundation.org/blog/power-to-the-people-making-freebsd-a-first-class-citizen-on-power/'>POWER to the People: Making FreeBSD a First Class Citizen on POWER</a>.
</p>
</li>
<li><p><a href='https://www.freebsdfoundation.org/blog/project-update-toolchain-modernization/'>Development Project Update: Toolchain Modernization</a>.
</p>
</li></ul>
Read more about our conference adventures in the conference recaps and trip
<p>reports in <a href='https://www.freebsdfoundation.org/news-and-events/newsletter/'>our monthly newsletters</a>.
</p>
<p>We help educate the world about FreeBSD by publishing the professionally
produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is
now a free publication. <a href='https://www.FreeBSDfoundation.org/journal/'>Find out more and access the latest issues</a>.
</p>
<p><a href='https://www.FreeBSDfoundation.org/news-and-events/'>You can find out more about events we attended and upcoming events here</a>.
As is the case for most of
us in this industry, SCALE was the last event we will be attending for a few
months. However, we're already working on how we can make more on-line
tutorials and how-to guides available to facilitate getting more folks to try
out FreeBSD. In the meantime, please check out the how-to guides we already
have available!
</p>
<p>We have continued our work with a new website developer to help us improve our
website. Work has begun to make it easier for community members to find
information more easily and to make the site more efficient.
</p>
<h3>Legal/FreeBSD IP</h3>
<p>The Foundation owns the FreeBSD trademarks, and it is our responsibility to
protect them. We also provide legal support for the core team to investigate
questions that arise.
</p>
<p>Go to http://www.FreeBSDfoundation.org/ to find out how we support FreeBSD and
how we can help you!
</p></body></project>
<project cat='team'>
<title>FreeBSD Core Team</title>
<contact>
<person>
<name>FreeBSD Core Team</name>
<email>core@FreeBSD.org</email>
</person>
</contact>
<body><p>The FreeBSD Core Team is the governing body of FreeBSD.
</p>
<ul>
<li><p>Core approved a source commit bit for Alfredo Dal'Ava Júnior. Alfredo has
been working on powerpc64 support. Justin Hibbits (jhibbits) will mentor
Alfredo.
</p>
</li>
<li><p>Core approved a source commit bit for Ryan Moeller. Ryan has been working on
porting ZoL to FreeBSD. Alexander Motin (mav) and Matt Macy (mmacy) will
mentor Ryan.
</p>
</li>
<li><p>Core approved a source commit bit for Nick O'Brien. Nick has been working on
RISC-V at Axiado. Kristof Provost (kp) and Philip Paeps (philip) will mentor
Nick.
</p>
</li>
<li><p>Core approved a source commit bit for Richard Scheffenegger. Richard has been
contributing TCP work. Michael Tuexen (tuexen) will mentor Richard and Rodney
Grimes (rgrimes) will act as co-mentor.
</p>
</li>
<li><p>Core approved a source commit bit for Aleksandr Fedorov. Aleksandr has been
testing and reviewing bhyve networking code. Vincenzo Maffione (vmaffione)
will mentor Aleksandr and John Baldwin (jhb) will act as co-mentor.
</p>
</li>
<li><p>Core requested that the freebsd-mobile@ list be retired as it was almost
exclusively receiving spam. postmaster@ completed core's request.
</p>
</li>
<li><p>Core approved third party authentication for some project services with
certain conditions. For example, for authentication with Google, users must
be using a FreeBSD.org account with two-factor authentication enabled. For
GitHub, we will enable and force multi-factor authentication for our
organization.
</p>
</li>
<li><p>The Core-initiated Git Transition Working Group continued to meet over the
first quarter of 2020. Their report is still forthcoming.
</p></li></ul>
</body></project>
<project cat='team'>
<title>FreeBSD Release Engineering Team</title>
<contact>
<person>
<name>FreeBSD Release Engineering Team</name>
<email>re@FreeBSD.org</email>
</person>
</contact>
<links>
<url href='https://www.freebsd.org/releases/11.4R/schedule.html'>FreeBSD 11.4-RELEASE schedule</url>
<url href='https://www.freebsd.org/releases/12.2R/schedule.html'>FreeBSD 12.2-RELEASE schedule</url>
<url href='https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/'>FreeBSD development snapshots</url>
</links>
<body><p>The FreeBSD Release Engineering Team is responsible for setting
and publishing release schedules for official project releases
of FreeBSD, announcing code freezes and maintaining the
respective branches, among other things.
</p>
<p>The FreeBSD Release Engineering Team published the schedules for the upcoming
11.4-RELEASE and 12.2-RELEASE cycles.
</p>
<p>Much time was spent by Glen Barber working on updates to the various build
tools adding support for builds from both Subversion and Git. This is very
much a work in progress, as there are a number of inter-connected moving
parts.
</p>
<p>Additionally throughout the quarter, several development snapshots builds
were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
</p>
<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
and the FreeBSD Foundation.
</p></body></project>
<project cat='team'>
<title>Cluster Administration Team</title>
<contact>
<person>
<name>Cluster Administration Team</name>
<email>clusteradm@FreeBSD.org</email>
</person>
</contact>
<links>
<url href='https://www.freebsd.org/administration.html#t-clusteradm'>Cluster Administration Team members</url>
</links>
<body><p>The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following:
</p>
<ul>
<li><p>Upgrade all ref- and universe- machines
</p></li>
<li><p>South Africa mirror (JINX) is online
</p></li>
<li><p>Package service of Seattle, USA mirror (TUK) is online
</p></li>
<li><p>Ongoing systems administration work:
</p><ul>
<li><p>Creating accounts for new committers.
</p></li>
<li><p>Backups of critical infrastructure.
</p></li>
<li><p>Keeping up with security updates in 3rd party software.
</p>
</li></ul>
</li></ul>
Work in progress:
<ul>
<li><p>Setup Malaysia (KUL) mirror
</p></li>
<li><p>Setup Brazil (BRA) mirror
</p></li>
<li><p>Setup Amsterdam (PKT) mirror
</p></li>
<li><p>Review the service jails and service administrators operation.
</p></li>
<li><p>Infrastructure of building aarch64 and powerpc64 packages
</p><ul>
<li><p>NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder.
</p></li>
<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
</p></li>
<li><p>Boot issues with Aarch64 reference machines.
</p></li></ul>
</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
</p></li>
<li><p>Prepare resource for git working group
</p></li>
<li><p>Searching for more mirror providers
</p><ul>
<li><p>https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout
</p></li>
<li><p>https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror
</p></li></ul>
</li></ul>
</body></project>
<project cat='team'>
<title>Continuous Integration</title>
<links>
<url href='https://ci.FreeBSD.org'>FreeBSD Jenkins Instance</url>
<url href='https://ci.FreeBSD.org/hwlab'>FreeBSD Hardware Testing Lab</url>
<url href='https://artifact.ci.FreeBSD.org'>FreeBSD CI artifact archive</url>
<url href='https://hackmd.io/@FreeBSD-CI'>FreeBSD CI weekly report</url>
<url href='https://wiki.freebsd.org/Jenkins'>FreeBSD Jenkins wiki</url>
<url href='https://wiki.freebsd.org/HostedCI'>Hosted CI wiki</url>
<url href='https://wiki.freebsd.org/3rdPartySoftwareCI'>3rd Party Software CI</url>
<url href='https://preview.tinyurl.com/y9maauwg'>Tickets related to freebsd-testing@</url>
<url href='https://github.com/freebsd/freebsd-ci'>FreeBSD CI Repository</url>
</links>
<contact>
<person>
<name>Jenkins Admin</name>
<email>jenkins-admin@FreeBSD.org</email>
</person>
<person>
<name>Li-Wen Hsu</name>
<email>lwhsu@FreeBSD.org</email>
</person>
</contact>
<body><p>Contact: <a href='https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing'>freebsd-testing Mailing List</a><br />
Contact: IRC #freebsd-ci channel on EFNet<br />
</p>
<p>The FreeBSD CI team maintains the continuous integration system and related tasks
for the FreeBSD project. The CI system regularly checks the committed changes
can be successfully built, then performs various tests and analysis of the
results. The artifacts from the build jobs are archived in the artifact server for
further testing and debugging needs. The CI team members examine the
failing builds and unstable tests and work with the experts in that area to
fix the codes or adjust test infrastructure. The details of these efforts
are available in the <a href='https://hackmd.io/@FreeBSD-CI'>weekly CI reports</a>.
</p>
<p>During the first quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
</p>
<p>Important changes:
</p><ul>
<li><p>All the -head jobs are using clang/lld toolchain
</p></li>
<li><p>All the -head test are using kyua in the base
</p></li>
<li><p>RISC-V jobs now generate full disk image and run tests in QEMU with OpenSBI
</p></li>
<li><p>freebsd-doc job also checks building of www.freebsd.org
</p>
</li></ul>
New jobs added:
<ul>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/
</p></li>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-images/
</p></li>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-testvm/
</p>
</li></ul>
Work in progress:
<ul>
<li><p>Collecting and sorting CI tasks and ideas <a href='https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo'>here</a>
</p></li>
<li><p>Setup the CI stage environment and put the experimental jobs on it
</p></li>
<li><p>Implementing automatic tests on bare metal hardware
</p></li>
<li><p>Adding drm ports building test against -CURRENT
</p></li>
<li><p>Testing and merging pull requests in <a href='https://github.com/freebsd/freebsd-ci/pulls'>the FreeBSD-ci repo</a>
</p></li>
<li><p>Planning for running ztest and network stack tests
</p></li>
<li><p>Helping more 3rd software get CI on FreeBSD through a hosted CI solution
</p></li>
<li><p>Adding non-x86 test jobs.
</p></li>
<li><p>Adding external toolchain related jobs.
</p></li>
<li><p>Adding more hardware to the hardware lab
</p>
</li></ul>
Please see freebsd-testing@ related tickets for more WIP information, and join the efforts
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='team'>
<title>Ports Collection</title>
<links>
<url href='https://www.FreeBSD.org/ports/'>About FreeBSD Ports</url>
<url href='https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html'>Contributing to Ports</url>
<url href='http://portsmon.freebsd.org/index.html'>FreeBSD Ports Monitoring</url>
<url href='https://www.freebsd.org/portmgr/index.html'>Ports Management Team</url>
</links>
<contact>
<person>
<name>René Ladan</name>
<email>portmgr-secretary@FreeBSD.org</email>
</person>
<person>
<name>FreeBSD Ports Management Team</name>
<email>portmgr@FreeBSD.org</email>
</person>
</contact>
<body><p>The Ports Management Team is responsible for overseeing the
overall direction of the Ports Tree, building packages, and
personnel matters. Below is what happened in the last quarter.
</p>
<p>During the last quarter the number of ports settled in at 39,000.
There are currently just over 2,400 open PRs of which 640 are
unassigned. The last quarter saw 8146 commits by 173 committers
to the HEAD branch and 357 commits by 52 committers to the
2020Q1 branch. This means the number of PRs grew although the
committer activity remained more or less constant.
</p>
<p>As always, people come and go. This time we welcomed Loïc
Bartoletti (lbartoletti@), Mikael Urankar (mikael@), Kyle Evans
(kevans@, who is already a src committer), and Lorenzo Salvadore
(salvadore@, who we already know for compiling these reports you
are reading right now). We said goodbye to dbn@ and theraven@,
who we hope to see back in the future.
</p>
<p>On the infrastructure side, USES=qca was added and USES=zope was
removed. The latter was also due to it was incompatible with
Python 3, and portmgr is in the process of removing Python 2.7 from
the Ports Tree. This means that all ports that currently rely on
Python 2.7 need to be updated to work with Python 3 or be removed.
</p>
<p>After a long period of work by multiple people, Xorg got updated
from the 1.18 to the 1.20 release series. Also, the web browsers
were updated: Firefox to version 75.0, Firefox ESR to 68.7.0, and
Chromium to 80.0.3987.149. The package manager itself got updated
to version 1.13.2.
</p>
<p>antoine@ ran 29 exp-runs during the last quarter for various updates
to KDE, poppler, pkg and build tools; and test compatibility with src
changes: removing procfs-based debugging, fixing TLS alignment, and
only including libssp_nonshared.a in libc for the i386 and Power
architectures.
</p></body></project>
<project cat='team'>
<title>FreeBSD Graphics Team status report</title>
<links>
<url href='https://github.com/FreeBSDDesktop'>Project GitHub page</url>
</links>
<contact>
<person>
<name>FreeBSD Graphics Team</name>
<email>x11@freebsd.org</email>
</person>
<person>
<name>Niclas Zeising</name>
<email>zeising@freebsd.org</email>
</person>
</contact>
<body><p>The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics
stack.
This includes graphics drivers, graphics libraries such as the
MESA OpenGL implementation, the X.org xserver with related libraries and
applications, and Wayland with related libraries and applications.
</p>
<p>The biggest highlight by far during the previous quarter was the long awaited
update of <code>xorg-server</code> to version 1.20.
After years of work by many people, this update finally landed in the form of
<code>xorg-server</code> 1.20.7.
With this update came a couple of new things, most notably, FreeBSD 12 and later
was switched to use the udev/evdev backend by default for handling input
devices, such as mice and keyboards.
Together with this release, the OpenGL library implementation <code>mesa</code> was
switched to use DRI3 by default, instead of the older DRI2.
</p>
<p>These updates caused some fallout when they first were comitted, most notably
issues with keyboards.
But with help from Michael Gmelin and others on the mailing lists, most issues
were sorted fast.
Unfortunately version 304 of the nVidia graphics driver is no longer supported
as of this release.
</p>
<p>Since this update, xorg-server has also been bumped to 1.20.8, which is the
latest upstream release.
</p>
<p>Apart from this update, there has also been ongoing work to keep the various
drm-kmod ports and packages up to date, mostly in response to changes in FreeBSD
CURRENT and to security issues found in the Intel i915 driver.
</p>
<p>We have also done updates as needed to keep the graphics and input stack up to
date and working, and deprecated and removed several old and no longer used
drivers, applications and libraries.
</p>
<p>We have also continued our regularly scheduled bi-weekly meetings.
</p>
<p>People who are interested in helping out can find us on the x11@FreeBSD.org
mailing list, or on our gitter chat: (https://gitter.im/FreeBSDDesktop/Lobby).
We are also available in #freebsd-xorg on EFNet.
</p>
<p>We also have a team area on GitHub where our work repositories can be found:
(https://github.com/FreeBSDDesktop)
</p></body></project>
<project cat='proj'>
<title>NFS over TLS implementation</title>
<contact>
<person>
<name>Rick Macklem</name>
<email>rmacklem@freebsd.org</email>
</person>
</contact>
<body><p>In an effort to improve NFS security, an internet draft
which I expect will become and RFC soon specifies the
use of TLS 1.3 to encrypt all data traffic on a Sun RPC
connection used for NFS.
</p>
<p>Although NFS has been able to use sec=krb5p to encrypt data
on the wire, this requires a Kerberos environment and, as
such, has not been widely adopted. It also required that
encryption/decryption be done in software, since only the
RPC message NFS arguments are encrypted.
Since Kernel TLS is capable of using hardware assist to
improve performance and does not require Kerberos, NFS
over TLS may be more widely adopted, once implementations
are available.
</p>
<p>Since FreeBSD's kernel TLS requires that data be in ext_pgs
mbufs for transmission, most of the work so far has been
modifying the NFS code that builds the protocol arguments
to optionally use ext_pgs mbufs.
Coding changes to handle received ext_pgs mbufs has also
been done, although this may not be required by the receive
kernel TLS.
</p>
<p>The kernel RPC has also been modified to do the STARTTLS
Null RPC and to do upcalls to userland daemons that
perform the SSL_connect()/SSL_accept(), since the kernel
TLS does not do this initial handshake.
So far only a self signed certificate on the server,
with no requirement for the client to have a certificate
has been implemented.
</p>
<p>Work is still needed to be done for the case where the NFS
client is expected to have a signed certificate. In particular,
it is not obvious to me what the correct solution is for
clients that do not have a fixed IP address/DNS name.
The code now is about ready for testing, but requires that
the kernel TLS be able to support receive as well as transmit.
Patches to the kernel TLS for receive are being worked on
by jhb@freebsd.org.
</p>
<p>Once receive side kernel TLS becomes available, the code in
subversion under base/projects/nfs-over-tls will need third
party testing and a security evaluation by someone familiar
with TLS.
</p>
</body></project>
<project cat='proj'>
<title>Import of the Kyua test framework</title>
<links>
<url href='https://wiki.freebsd.org/TestSuite'>The FreeBSD Test Suite</url>
</links>
<contact>
<person>
<name>Brooks Davis</name>
<email>brooks@FreeBSD.org</email>
</person>
</contact>
<body><p>The FreeBSD test suite uses the Kyua test framework to run tests.
</p>
<p>Historically Kyua has been installed from the ports collection
(<code>devel/kyua</code>). While this is fine for mainstream architectures,
it can pose bootstrapping issues on new architectures and package
installation is quite slow under emulation or on FPGA based systems.
By including it in the FreeBSD base system we can avoid these issues.
</p>
<p>We hope that this inclusion will spur testing of embedded platforms
and simplify the process of testing within continuous integration
systems.
</p>
<p>We currently plan to retain the <code>devel/kyua</code> port to serve FreeBSD
versions without and to serve as a development version.
</p>
<p>Sponsor: DARPA
</p></body></project>
<project cat='proj'>
<title>Linux compatibility layer update</title>
<contact>
<person>
<name>Edward Tomasz Napierala</name>
<email>trasz@FreeBSD.org</email>
</person>
</contact>
<body><p>Work during this quarter focused on source code cleanup and making
it easier to debug missing functionality. There were, however,
some user-visible changes: added support for <code>TCP_CORK</code> as required by Nginx,
added support <code>MAP_32BIT</code> flag, which fixes Mono binaries from Ubuntu Bionic,
and a fix for DNS resolution with glibc newer than 2.30, which affected
CentOS 8.
</p>
<p>The Linux Test Project tests that are being run as part of the
the <a href='https://ci.FreeBSD.org'>FreeBSD Continuous Integration infrastructure</a>
now include the Open POSIX test suite.
</p>
<p>There's still a lot to do:
</p>
<ul>
<li><p>There are pending reviews for patches that add
<a href='https://reviews.freebsd.org/D13209'>extended attributes support</a>,
and <a href='https://reviews.freebsd.org/D10275'>fexecve(2) syscall</a>, and
they require wrapping up and committing
</p>
</li>
<li><p>There are over <a href='https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/'>400 failing LTP tests</a>.
Some of them are false positives, some are easy to fix bugs, and some require adding
new system calls. Any help is welcome.
</p>
</li></ul>
Sponsor: The FreeBSD Foundation
</body></project>
<project cat='proj'>
<title>syzkaller on FreeBSD</title>
<contact>
<person>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</person>
<person>
<name>Michael Tuexen</name>
<email>tuexen@FreeBSD.org</email>
</person>
</contact>
<body><p>See the syzkaller entry in the 2019q1 quarterly report for an
introduction to syzkaller.
</p>
<p>A number of kernel bugs have been found by syzkaller and fixed this
quarter, mostly in the network stack and file descriptor table code.
Bug investigations have led to improvements in debugging facilities and
assertions, for example in the SCTP stack. Syzkaller reproducers have
been added to Peter Holm's stress2 suite, helping ensure that
regressions are found quickly.
</p>
<p>The syzkaller instance hosted by backtrace.io (see the 2019q3 report)
has been very useful in testing syzkaller improvements and finding bugs.
Though Google runs a dedicated syzkaller instance <a href='https://syzkaller.appspot.com/freebsd'>targeting FreeBSD</a>,
it has proved fruitful to run multiple instances since they end up
building different corpuses and thus discover different, though
overlapping, sets of bugs.
</p>
<p>Support for fuzzing a number of new system calls has been added,
including the new copy_file_range() and __realpathat() system calls,
and the Capsicum system calls. Some work was also done to audit
existing system call definitions to ensure that FreeBSD-specific
extensions of POSIX system calls are covered. Work is ongoing to target
the Linux emulation layer, and to collect kernel dumps so that one-off
crashes with no reproducer have a chance at being diagnosed and fixed.
</p>
<p>Sponsor: backtrace.io
Sponsor: The FreeBSD Foundation
</p>
</body></project>
<project cat='kern'>
<title>if_bridge</title>
<contact>
<person>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</person>
</contact>
<body><p>The current implementation of if_bridge uses a single mutex to protect its
internal data structures. As a result it’s nowhere near as fast as it could be.
This is relevant for users who want to run many vnet jails or virtual machines
bridged together, for example.
</p>
<p>As part of this project several new tests have already been added for
if_bridge. These are generally very useful for validating any locking changes,
and will also help to prevent regressions for other future changes. These
tests live in /usr/tests/sys/net/if_bridge_test.
</p>
<p>The current work is concentrating on investigating if it's possible to leverage
the ConcurrencyKit epoch code for the datapath (i.e. <code>bridge_input()</code>,
<code>bridge_output()</code>, <code>bridge_forward()</code>, ...).
</p>
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='kern'>
<title>sigfastblock(2)</title>
<contact>
<person>
<name>Konstantin Belousov</name>
<email>kib@FreeBSD.org</email>
</person>
</contact>
<body><p>Rtld services need to be async signal safe. This is needed, for
instance, to provide working symbol bindings in signal handlers.
</p>
<p>For threaded processes, libthr interposes all user-installed signal
handlers and saves the signals and related context if signal is
delivered while rtld or libthr are in protected section of code.
</p>
<p>In non-threaded processes, the async safety is provided by changing
signal mask for the thread. It is actually better than the
interposing done by libthr, since signals are delivered in the right
context, instead of libthr attempt of recreate it later. But the
unfortunate side-effect is that each rtld entry requires two syscalls,
one to set mask, and one to restore it. Typically this adds around 40
or more syscalls on each process startup. Worse, rtld services used
by typical language runtime exception handling systems also have the
cost of signal mask manipulation.
</p>
<p>The new sigfastblock(2) syscall was added that allows thread to
designate a memory location as fast signal block. If this word
contains non-zero value, kernel interprets the thread state same as if
all blockable signals are blocked. The facility drastically improves
exception handling speed on FreeBSD.
</p>
<p>Since signals might abort interruptible sleeps, initial implementation
read the blocking word on each syscall entry. This is needed to
ensure that userspace does not see spurious EINTR/ERESTART if the
signals are blocked by the word. Since if kernel cached outdated
value for the block word, it would abort sleep, but then ast sees the
correct mask and does not deliver the pending signal.
</p>
<p>There were concerns that this read of the word causes slowdown in
syscalls microbenchmarks, esp. on machines with SMAP. The reason is
that SMAP requires all userspace access bracketed by STAC/CLAC pair of
instructions, which are de-facto serializing (this is not
architectural, but all current microarchitectures do it). The
decision was made to eliminate the word read, at the cost of possibly
returning spurious EINTR. The impact should be minimal, since
sigfastblock(2) is not supposed to be the service available to users,
it is only assumed for rtld and libthr implementations.
</p>
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='kern'>
<title>arm64 LSE atomic instructions</title>
<contact>
<person>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</person>
</contact>
<body><p>An investigation of some performance oddities on EC2 Graviton 2
instances resulted in support for the use of Large System Extension
(LSE) atomic instructions in the FreeBSD kernel.
</p>
<p>LSE is an mandatory ISA extension specified in ARMv8.1. It consists of
a number of new atomic instructions, superseding the
Load-Linked/Store-Conditional (LL/SC) instruction pairs use when LSE is
not implemented. The extension is present in a number of ARMv8 server
platforms, including the Cavium ThunderX2 and AWS Graviton 2. The new
instructions provide significantly better scalability.
</p>
<p>A recent set of patches modified the FreeBSD kernel to detect support
for LSE and dynamically select an atomic(9) implementation based on
the new instructions when all CPUs implement the extension. The initial
atomic(9) implementations were provided by Ali Saidi. Some benchmarking
on a 64-vCPU Graviton 2 instance shows a ~4% reduction in wall clock
time for a kernel build, and a ~15% reduction in system CPU time.
</p>
<p>Some ARMv8 multi-processor systems implement a heterogenous CPU
architecture, referred to as big.LITTLE, in which multiple processor
types are used. Surprisingly, such systems may implement the LSE on
only a subset of its CPUs, in which case LSE instructions cannot be used
by the kernel. As a result, FreeBSD currently waits until all
processors are online before selecting the atomic(9) implementation,
which precludes the use of ifuncs to provide dynamic selection.
</p>
<p>Currently atomic(9)'s use of LSE is limited to the kernel. A future
project would extend this to userspace, so that FreeBSD system libraries
can leverage the LSE instructions when they are available.
</p>
<p>Sponsor: The FreeBSD Foundation
Sponsor: Amazon
</p></body></project>
<project cat='kern'>
<title>FreeBSD on Microsoft HyperV and Azure</title>
<links>
<url href='https://wiki.freebsd.org/MicrosoftAzure'>FreeBSD on MicrosoftAzure wiki</url>
<url href='https://wiki.freebsd.org/HyperV'>FreeBSD on Microsoft HyperV</url>
</links>
<contact>
<person>
<name>FreeBSD Integration Services Team</name>
<email>bsdic@microsoft.com</email>
</person>
<person>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</person>
<person>
<name>Li-Wen Hsu</name>
<email>lwhsu@FreeBSD.org</email>
</person>
</contact>
<body><p>Wei is working on HyperV Socket support for FreeBSD. HyperV Socket provides a way for the HyperV host and guest to communicate using a common socket interface without networking required. Some features in Azure require HyperV Socket support in the guest.
</p>
<p>Details of HyperV Socket is available <a href='https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service'>here</a>.
</p>
<p>The work-in-progress is available <a href='https://reviews.freebsd.org/D24061'>here</a>
</p>
<p>This project is sponsored by Microsoft.
</p>
<p>Li-Wen is working on the FreeBSD release code related to Azure for the -CURRENT and 12-STABLE branches. The release of 12.1-RELEASE on Azure is also in progress.
</p>
<p>The work-in-progress is available <a href='https://reviews.freebsd.org/D23804'>here</a>
</p>
<p>This project is sponsored by The FreeBSD Foundation.
</p></body></project>
<project cat='kern'>
<title>FreeBSD on the ARM Morello platform</title>
<links>
<url href='https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-morello.html'>The Arm Morello Board</url>
<url href='https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/'>The CHERI Project</url>
</links>
<contact>
<person>
<name>Andrew Turner</name>
<email>andrew@FreeBSD.org</email>
</person>
<person>
<name>Ruslan Bukin</name>
<email>br@FreeBSD.org</email>
</person>
<person>
<name>Brooks Davis</name>
<email>brooks@FreeBSD.org</email>
</person>
<person>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</person>
<person>
<name>Robert Watson</name>
<email>rwatson@FreeBSD.org</email>
</person>
</contact>
<body><p>CHERI (Capability Hardware Enhanced RISC Instructions) extends
conventional hardware Instruction-Set Architectures (ISAs) with new
architectural features to enable fine-grained memory protection and
highly scalable software compartmentalization. The CHERI
memory-protection features allow historically memory-unsafe programming
languages such as C and C++ to be adapted to provide strong, compatible,
and efficient protection against many currently widely exploited
vulnerabilities. The CHERI scalable compartmentalization features enable
the fine-grained decomposition of operating-system (OS) and application
code, to limit the effects of security vulnerabilities in ways that are
not supported by current architectures. CHERI is a hybrid capability
architecture in that it is able to blend architectural capabilities with
conventional MMU-based architectures and microarchitectures, and with
conventional software stacks based on virtual memory and C/C++. This
approach allows incremental deployment within existing ecosystems, which
we have demonstrated through hardware and software prototyping.
</p>
<p>On 18 October 2019, Arm announced Morello, an experimental
CHERI-extended, multicore, superscalar ARMv8-A processor, System-on-Chip
(SoC), and prototype board to be available from late 2021. Morello is a
part of the UKRI £187M Digital Security by Design Challenge (DSbD)
supported by the UK Industrial Strategy Challenge Fund, including a
commitment of over £50M commitment by Arm. The aim is to test and
validate CHERI extensions to the Arm ISA at scale with the idea that
"successful concepts are expected to be carried forward into the
architecture." The Morello board is scheduled to ship in the third
quarter of 2021.
</p>
<p>Over the past decade we have developed CheriBSD, a version of FreeBSD
supporting CHERI. Our public facing work has been performed on MIPS64
and more recently on RISC-V. Andrew has also developed a port to an
earlier version of the Morello ISA which we will be merging into
our public repository as simulators and compilers become available.
</p>
<p>The Morello board is based on the Arm Neoverse N1 platform and derived
from the N1SDP development platform. (The AWS Graviton2 systems are
also based on the N1 core.) Ruslan and Andrew are currently
working to enable all relevant features of the N1 and the N1SDP to give
us a solid baseline for work on Morello. These features include the
PCI root complex, system memory management unit (SMMU), and CoreSight.
To the extent practical we are upstreaming these features to FreeBSD.
</p>
<p>Sponsor: DARPA, UKRI
</p></body></project>
<project cat='kern'>
<title>NXP ARM64 SoC support</title>
<contact>
<person>
<name>Marcin Wojtas</name>
<email>mw@semihalf.com</email>
</person>
<person>
<name>Artur Rojek</name>
<email>ar@semihalf.com</email>
</person>
<person>
<name>Dawid Gorecki</name>
<email>dgr@semihalf.com</email>
</person>
</contact>
<body><p>The Semihalf team initiated working on FreeBSD support for the
<a href='https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A'>NXP LS1046A SoC</a>
</p>
<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
integrated packet processing acceleration and high speed peripherals
including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
range of networking, storage, security and industrial applications.
</p>
<p>Completed since the last update:
</p><ul>
<li><p>Clean-up and rebase support on top of FreeBSD-HEAD. Prepare features
for the upstream submission:
</p><ul>
<li><p>QorIQ platform clockgen driver
</p></li>
<li><p>LS1046A clockgen driver
</p></li>
<li><p>GPIO support for QorIQ boards
</p></li>
<li><p>QorIQ LS10xx AHCI driver
</p></li>
<li><p>VF610 I2C controller support
</p></li>
<li><p>TCA6416 GPIO expander
</p></li>
<li><p>Epson RX-8803 RTC
</p></li>
<li><p>QorIQ LS10xx SDHCI driver
</p>
</li></ul>
</li></ul>
Todo:
<ul>
<li><p>Upstreaming of developed features. This work is expected to
be submitted/merged to HEAD in the Q2 of 2020.
</p>
</li></ul>
Sponsor: Alstom Group
</body></project>
<project cat='kern'>
<title>ENA FreeBSD Driver Update</title>
<links>
<url href='https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README'>ENA README</url>
</links>
<contact>
<person>
<name>Michal Krawczyk</name>
<email>mk@semihalf.com</email>
</person>
<person>
<name>Maciej Bielski</name>
<email>mba@semihalf.com</email>
</person>
<person>
<name>Marcin Wojtas</name>
<email>mw@semihalf.com</email>
</person>
</contact>
<body><p>ENA (Elastic Network Adapter) is the smart NIC available in the
virtualized environment of Amazon Web Services (AWS). The ENA
driver supports multiple transmit and receive queues and can handle
up to 100 Gb/s of network traffic, depending on the instance type
on which it is used.
</p>
<p>Completed since the last update:
</p><ul>
<li><p>Upstream of the driver to v2.1.1, introducing:
</p><ul>
<li><p>Bug fix for LLQ mode which was causing race when multiple IO queues were
used
</p>
</li></ul>
</li></ul>
Work in progress:
<ul>
<li><p>Last touches for ENA v2.2.0 release, introducing:
</p><ul>
<li><p>Add driver support for the upcoming HW features (like Rx offsets,
reporting Tx drops)
</p></li>
<li><p>Add sysctl tuneables for IO queue number
</p></li>
<li><p>Create IO queues with optional size backoff
</p></li>
<li><p>Rework the way of configration of drbr and Rx ring size to be more robust
and stable
</p></li>
<li><p>New HAL version
</p></li>
<li><p>Other minor fixes and improvements
</p>
</li></ul>
</li></ul>
Sponsor: Amazon.com Inc
</body></project>
<project cat='arch'>
<title>FreeBSD/powerpc Project</title>
<contact>
<person>
<name>Mark Linimon</name>
<email>linimon@FreeBSD.org</email>
</person>
<person>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</person>
<person>
<name>Piotr Kubaj</name>
<email>pkubaj@FreeBSD.org</email>
</person>
</contact>
<body><p>The FreeBSD/powerpc project continues to mature.
</p>
<p>In addition to the above listed people, we want to acknowledge
contributions from adalava, bdragon, luporl, and mikael, among
others.
</p>
<p>Key points:
</p>
<ul>
<li><p>On -CURRENT, all platforms have been switched to the
LLVM 10.0 compiler and lld10. Thus, ld.bfd has been removed
from base.
</p></li>
<li><p>On powerpc64, -CURRENT has been switched to the ELFv2 ABI.
Older versions of -CURRENT that either used GCC, or LLVM with
the ELFv1 ABI, are no longer supported.
</p></li>
<li><p>On powerpc64 FreeBSD-STABLE (11 and 12), the platforms still
remain on the antique gcc4.2.1 in base. Note: that version of
GCC has been removed from the -CURRENT src tree. Support for
this configuration is now a "best-effort" status.
</p></li>
<li><p>On powerpc (32-bit), the ABI did not change as with powerpc64,
so upgrading should be easier than with powerpc64.
</p>
</li></ul>
Hardware status:
<ul>
<li><p>The aacraid(4) driver has been been fixed for big-endian, thanks
to luporl. This means that Talos customers who got the SAS option
can now use the onboard SAS.
</p></li>
<li><p>The ixl(4) driver has also been fixed for big-endian, also thanks
to luporl.
</p>
</li></ul>
Software status:
<ul>
<li><p>As a result of -CURRENT switching to LLVM/ELFv2, ifuncs became
available, meaning that we now have optimized memcpy/bcopy and
strncpy functions when running on processors that supports VSX
instructions.
</p></li>
<li><p>powerpc64 is now able to run on QEMU without the need of
Huge Pages support.
</p></li>
<li><p>The virtio drivers have been fixed.
</p></li>
<li><p>kernel minidump has been fixed.
</p>
</li></ul>
Package status:
<ul>
<li><p>A FreeBSD.org package set is available for powerpc64/12
(quarterly). The -quarterly build has just been rebased
from 12.0 to 12.1, per the desupport of the older 12.0.
The first rebased build has been completed, with 29776
packages being available.
</p></li>
<li><p>We are currently working on the upgrade of the package
builder to a recent -CURRENT. Therefore, the available
packages for -CURRENT are still ELFv1, which are not useful.
Please contact Mark Linimon for more information.
</p></li>
<li><p>mesa has been switched to llvm90, which fixes certain
problems.
</p></li>
<li><p>Work continues on firefox and related ports.
</p></li>
<li><p>More ports fixes are being committed every day.
</p>
</li></ul>
The team would like to thank IBM for the loan of two POWER8 and one
<p>POWER9 machines, and Oregon State University (OSU) for providing the
hosting. As well, we would like to thank the clusteradm team for
keeping the Tyan POWER8 machines online that are hosted at
<a href='https://www.nyi.net'>NYI</a>.
</p>
<p>Also, Piotr would like to thank the FreeBSD Foundation for
funding his personal Talos, and Raptor (via its IntegriCloud
subsidiary) for loaning a server on which talos.anongoth.pl runs.
</p></body></project>
<project cat='arch'>
<title>FreeBSD/RISC-V Project</title>
<links>
<url href='https://wiki.freebsd.org/riscv'>Wiki</url>
</links>
<contact>
<person>
<name>Ruslan Bukin</name>
<email>br@FreeBSD.org</email>
</person>
<person>
<name>Mitchell Horne</name>
<email>mhorne@FreeBSD.org</email>
</person>
<person>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</person>
<person>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</person>
<person>
<name>Philip Paeps</name>
<email>philip@FreeBSD.org</email>
</person>
</contact>
<body><p>Contact: <a href='https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv'>freebsd-riscv Mailing List</a><br />
Contact: IRC #freebsd-riscv channel on freenode<br />
</p>
<p>It has been a year since the RISC-V project's last status report. In that time,
the RISC-V port has benefited from increased attention, and received
improvements of all kinds.
</p>
<p>The RISC-V project has brought in two new src committers. We'd like to welcome
Jessica Clarke (jrtc27@), who is a member of CheriBSD, and Nick O'Brien (nick@)
of Axiado to the team.
</p>
<p>Some highlights from last year:
</p><ul>
<li><p>Bring-up on SiFive's Hifive Unleashed board
</p></li>
<li><p>Support for the OpenSBI firmware and version 0.2 of the SBI specification
</p></li>
<li><p>Addition of the UART, SPI, and PRCI device drivers for the HiFive Unleashed
</p>
</li></ul>
Last quarter, the default compiler and linker was switched to clang/lld. This
<p>required a small number of integration changes on our side, but was mainly
enabled by the upstream improvements to the RISC-V LLVM back-end. LLVM's RISC-V
support became "official" <a href='https://lists.llvm.org/pipermail/llvm-dev/2019-September/135304.html'>with LLVM 9</a>, and LLVM 10 has brought further
improvements. The LLVM back-end is expected to continue to mature, as there are
now many parties actively involved in its development. GCC remains supported as
an external toolchain for RISC-V.
</p>
<p>The <a href='https://ci.freebsd.org/job/FreeBSD-head-riscv64-build/'>CI job for HEAD</a>
has been updated to use the clang/lld toolchain, and a GCC job will be added in the future.
The RISC-V disk image built in the CI system now contains the full base system and
is available on the <a href='https://artifact.freebsd.org'>CI artifact server</a> for
further testing. The CI test job was updated to use OpenSBI in qemu. Work on
running the FreeBSD test suite for RISC-V in the CI system is in progress.
</p>
<p>Some progress has been made on supporting the ports framework on RISC-V, which
was mostly untested until recently. First,
<code>emulators/qemu-user-static-devel</code> received an update adding support for the
RISC-V 64-bit ABI, allowing ports to be cross-compiled via <code>poudiere(8)</code>.
Second, improvements were made to the detection of the soft-float ABI,
riscv64sf. Systems running either of the hard-float or soft-float ABIs can now
compile and run ports natively. At the moment a small subset of ports can be
built successfully, and in the coming months we will look to improve that to
include a base set of crucial ports (e.g. python or perl).
</p>
<p>The CheriBSD project saw an initial port to RISC-V this quarter. Preliminary
support for the CHERI ISA has been added to the Spike and QEMU emulators, as
well as the necessary changes on the CheriBSD side. Currently, the CheriBSD
RISC-V kernel boots, and most statically compiled CHERI binaries run without
issue.
</p>
<p>Although real RISC-V hardware is still scarce, any users with an interest
trying out or contributing to the RISC-V port are encouraged to do so. Please
visit the recently updated wiki page for information on getting set up, or check
out "Getting Started with FreeBSD/RISC-V" in the January/February edition of The
FreeBSD Journal.
</p>
<p>Sponsor: DARPA, AFRL, Axiado, the FreeBSD Foundation
</p></body></project>
<project cat='bin'>
<title>GCC 4.2.1 Retirement</title>
<contact>
<person>
<name>Ed Maste</name>
<email>emaste@freebsd.org</email>
</person>
<person>
<name>Warner Losh</name>
<email>imp@freebsd.org</email>
</person>
</contact>
<body><p>In 2007 the GNU Compiler Collection (GCC) migrated to GPLv3, which
prompted discussions about the future of the FreeBSD tool chain. We held
a <a href='https://wiki.freebsd.org/201005ToolchainSummit'>Tool Chain Summit</a> at
BSDCan 2010. Roman Divacky gave an update on the ClangBSD project, building
FreeBSD using the new and rapidly improving Clang compiler.
</p>
<p>Since that time Clang was imported into the FreeBSD base system and was used
more and more widely - first being installed but not the default <code>cc</code>, then
used by default on i386 and amd64, and later used on more and more targets.
In the years since Dimitry Andric has been keeping our copy of Clang
up-to-date.
</p>
<p>GCC 4.2.1 was kept in the tree for a few FreeBSD targets that hadn't migrated
to Clang, such as MIPS and Sparc64. By early this year all remaning targets
had migrated to external toolchain (contemporary GCC from ports or packages),
or had been deprecated.
</p>
<p>With no in-tree consumers remaining, GCC 4.2.1 was removed from FreeBSD in
<a href='https://svnweb.freebsd.org/changeset/base/358454'>r358454</a> on February 29,
2020.
</p>
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='bin'>
<title>elfctl utility</title>
<contact>
<person>
<name>Ed Maste</name>
<email>emaste@freebsd.org</email>
</person>
</contact>
<body><p>In <a href='https://reviews.freebsd.org/rS340076'>r340076</a> Ed added the
<i>NT_FREEBSD_FEATURE_CTL</i> ELF note, used to allow binaries to opt out of,
or in to, vulnerability mitigation and other features. FreeBSD Foundation
intern Bora Özarslan later added a tool to decode and modify the ELF note,
but it had yet to be installed by default.
</p>
<p>In the previous quarter Ed renamed the tool to <i>elfctl</i>, and installed it
in /usr/bin. Ed also committed a number of minor bug fixes, code style
improvements, etc.
</p>
<p>Usage examples - list known feature flags:
<pre><code>
$ elfctl -l
Known features are:
aslr Disable ASLR
protmax Disable implicit PROT_MAX
stackgap Disable stack gap
wxneeded Requires W+X mappings
</code></pre>
</p>
<p>List feature tags set on a binary:
<pre><code>
$ elfctl /bin/ls
File '/bin/ls' features:
aslr 'Disable ASLR' is unset.
protmax 'Disable implicit PROT_MAX' is unset.
stackgap 'Disable stack gap' is unset.
wxneeded 'Requires W+X mappings' is unset.
</code></pre>
</p>
<p>Indicate that a binary requests to opt-out of address randomization:
<pre><code>
$ elfctl -e +aslr binary
</code></pre>
</p>
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='bin'>
<title>ELF Tool Chain</title>
<contact>
<person>
<name>Ed Maste</name>
<email>emaste@freebsd.org</email>
</person>
</contact>
<body><p>A number of performance and functional improvements were committed to ELF
Tool Chain tools over the last quarter.
</p>
<p>FreeBSD Foundation intern Tiger Gao added DWARF Debug Information Entry
(DIE) caching to addr2line which provided a substantial improvement when
translating many entries (even surpassing GNU addr2line with a large list).
</p>
<p>Tiger also rebased and updated an upstream ELF Tool Chain submission to
handle <i>DW_AT_ranges</i> and addressed two elfcopy/objcopy bugs: setting the
OS/ABI field correctly when converting a binary file to ELF, and correctly
adding new sections when there is no <i>.shstrtab</i> section.
</p>
<p>Ed committed several readelf improvements, including decoding the
<i>PROTMAX_DISABLE</i>, <i>STKGAP_DISABLE</i>, and <i>WXNEEDED</i> ELF feature control
flags, decoding Xen and GNU Build-ID ELF notes, and improved input
validation.
</p>
<p>Mark Johnston addressed many memory and file descriptor leaks and similar
issues reported by Coverity Scan.
</p>
<p>Sponsor: The FreeBSD Foundation
</p></body></project>
<project cat='doc'>
<title>FreeBSD Translations on Weblate</title>
<links>
<url href='https://wiki.freebsd.org/DocTranslationOnWeblate'>Translate FreeBSD on Weblate wiki</url>
<url href='https://translate-dev.freebsd.org/'>FreeBSD Weblate Instance</url>
</links>
<contact>
<person>
<name>Danilo G. Baio</name>
<email>dbaio@FreeBSD.org</email>
</person>
<person>
<name>Edson Brandi</name>
<email>ebrandi@FreeBSD.org</email>
</person>
</contact>
<body><p>As announced on <a href='https://www.freebsd.org/news/newsflash.html#event20200121:01'>January</a>, The FreeBSD Project is adopting Weblate as its web-based continuous localization platform.
</p>
<p>We are getting new volunteers to the effort and so far these are the numbers:
</p>
<h3>Q1 2020 Status</h3>
<ul>
<li><p><b>10</b> languages
</p></li>
<li><p><b>47</b> registered users
</p>
</li></ul>
<h4>Languages</h4>
<ul>
<li><p>Chinese (Simplified) (zh_CN)
</p></li>
<li><p>Chinese (Traditional) (zh_TW) - <b><i>Added</i></b>
</p></li>
<li><p>French (fr_FR) - <b><i>Added</i></b>
</p></li>
<li><p>German (de_DE) - <b><i>Added</i></b>
</p></li>
<li><p>Italian (it_IT) - <b><i>Added</i></b>
</p></li>
<li><p>Norwegian Bokmål - <b><i>Added</i></b> - New language on FreeBSD
</p></li>
<li><p>Persian (fa_IR) - <b><i>Added</i></b> - New language on FreeBSD
</p></li>
<li><p>Portuguese (Brazil)
</p></li>
<li><p>Spanish
</p></li>
<li><p>Turkish (tr-TR) <b>[1]</b> - <b><i>Added</i></b> - New language on FreeBSD
</p>
</li></ul>
1 - Already had an effort in the past.
<p>We want to thank everyone that contributed, translating or reviewing documents.
</p>
<p>And please, help promote this effort on your local user group, we always need more volunteers.
</p></body></project>
<project cat='doc'>
<title>FreeBSD Manpages overhaul</title>
<contact>
<person>
<name>Gordon Bergling</name>
<email>gbergling@gmail.com</email>
</person>
</contact>
<body><p>I am currently working on an overhaul for the FreeBSD manpages by updating the HISTORY and STANDARDS sections and while here creating new manpages for parts of the system that missing documentation. FreeBSD has already one of the best documentation available for an UNIX-like operation system, but there are parts that could be improved.
</p>
<p>For the parts that have been already improved you can have a look at <a href='https://reviews.freebsd.org/p/gbergling_gmail.com/'>my Phabricator account</a>.
</p>
<p>If you would like to help on improving the documentation effort, please contact Benedict Reuschling <a href='mailto:bcr@freebsd.org'>bcr@freebsd.org</a> or me at gbergling@gmail.com.
</p></body></project>
<project cat='ports'>
<title>KDE on FreeBSD</title>
<links>
<url href='https://freebsd.kde.org/'>KDE FreeBSD</url>
<url href='https://community.kde.org/FreeBSD'>KDE Community FreeBSD</url>
</links>
<contact>
<person>
<name>Adriaan de Groot</name>
<email>kde@FreeBSD.org</email>
</person>
</contact>
<body><p>The <i>KDE on FreeBSD</i> project packages the software produced by
the KDE Community for FreeBSD. The software includes a
full desktop environment KDE Plasma, the art application
<a href='https://krita.org/'>Krita</a>, video editor <a href='https://kdenlive.org'>Kdenlive</a>
and hundreds of other applications that can be used on
any FreeBSD desktop machine.
</p>
<p>The quarter opened with a new kstars (amateur astronomy application)
release landing in ports, and then had the usual regular updates:
</p>
<ul>
<li><p>three KDE Frameworks releases (on a monthly schedule),
</p></li>
<li><p>three bugfix releases to the collection of KDE software from
the KDE release service (formerly <i>KDE Applications</i>, but it was
always more that only-applications),
</p></li>
<li><p>three bugfix releases to the KDE Plasma desktop.
</p>
</li></ul>
There were no substantial Qt updates but four bugfix releases for
<p><code>devel/cmake</code>, and regular work all over the ports tree.
</p>
<p>The SDDM login manager was updated to a much newer -- by over a year --
release and patched to support more FreeBSD features.
</p>
<p>One update to <code>devel/qca</code> dropped compatibility with FreeBSD 11
because upstream no longer supports older OpenSSL versions.
There is infrastructure in the ports tree now that adds a <code>USES=qca</code>
for Qt applications needing crypto support.
</p>
<p>The <a href='https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=New&bug_status=Open&bug_status=In%20Progress&bug_status=UNCONFIRMED&email1=kde%40FreeBSD.org&emailassigned_to1=1&emailtype1=substring&f0=OP&f1=OP&f2=product&f3=component&f4=alias&f5=short_desc&f7=CP&f8=CP&f9=assigned_to&j1=OR&j_top=OR&o2=substring&o3=substring&o4=substring&o5=substring&o9=substring&query_format=advanced&v2=kde%40&v3=kde%40&v4=kde%40&v5=kde%40&v9=kde%40&human=1'>open bugs list</a>
remains stable around 28 open issues,
with some interesting xkb issues as a highlight.
We welcome detailed bug reports
and patches. KDE packaging updates are prepared in
a <a href='https://github.com/freebsd/freebsd-ports-kde/'>copy of the ports repository</a>
on GitHub and then merged in SVN. We welcome pull requests
there as well.
</p>
</body></project>
<project cat='ports'>
<title>XFCE</title>
<contact>
<person>
<name>Guido Falsi</name>
<email>xfce@FreeBSD.org</email>
</person>
</contact>
<body><p>After the XFCE update to 4.14 a regression was observed in the XFCE
window manager xfwm4. It caused window decorations to be drawn wrong
or missing with certain graphic hardware setups. It has been reported
that the recent update to Xorg server in the ports tree fixes this
issue. The updated Xorg server will be available in the next
qurterly branch.
</p></body></project>
<project cat='ports'>
<title>Wine on FreeBSD</title>
<links>
<url href='https://www.winehq.org'>Wine homepage</url>
</links>
<contact>
<person>
<name>Gerald Pfeifer</name>
<email>gerald@FreeBSD.org</email>
</person>
<person>
<name>Lorenzo Salvadore</name>
<email>salvadore@FreeBSD.org</email>
</person>
</contact>
<body><p>The standard Wine port has moved from Wine 4.0.3 to Wine 5.0 which
represents over 7,400 individual changes including built-in modules in
PE format, multi-monitor support, Vulkan 1.1 support, and an XAudio2
re-implementation.
</p>
<p>After our request for help in the last quarterly report the i386 wine
ports have been adopted by salvadore who immediately started resolving
existing bugs and improving the ports. Most of this work is ready and we
began committing first pieces in March. Since it takes more time than
initially expected, we will also update the i386-wine-devel port during
this process so that users needing a more recent version can easily get it
from the ports tree (or binary packages). On the other hand, we plan on
backporting these improvements to i386-wine after i386-wine-devel is done
and only then update that port, so that we always guarantee a stable
version of i386-wine.
</p></body></project>
<project cat='ports'>
<title>Go on freebsd/arm64</title>
<links>
<url href='https://golang.org/doc/go1.14#freebsd'>Go 1.14 Release Notes </url>
</links>
<contact>
<person>
<name>Mikaël Urankar</name>
<email>mikael@FreeBSD.org</email>
</person>
<person>
<name>Dmitri Goutnik</name>
<email>dmgk@FreeBSD.org</email>
</person>
</contact>
<body><p>Starting from the recently released version 1.14, Go now officially supports
64-bit ARM architecture on FreeBSD 12.0 or later.
This porting effort was initially started by Greg V (aka myfreeweb) and resumed
by Shigeru Yamamoto, Dmitri Goutnik and Mikaël Urankar.
Dmitry has set up a CI builder to catch regression on FreeBSD aarch64 (it's
required by the golang policy for adding a new port to the main Go repository)
</p>
<p>Work in progress:
</p><ul>
<li><p>a lot of ports use an old version of golang.org/x/sys or golang.org/x/net
(to name a few) that doesn't contain the FreeBSD aarch64 bits,
work is being done to fix these ports (details are in the <a href='https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242312)'>bug tracker entry</a>
</p></li></ul>
</body></project>
<project cat='ports'>
<title>sysctlmibinfo2 API</title>
<links>
<url href='https://gitlab.com/alfix/sysctlmibinfo2'>sysctlmibinfo2</url>
</links>
<contact>
<person>
<name>Alfonso Sabato Siciliano</name>
<email>alfonso.siciliano@email.com</email>
</person>
</contact>
<body><p>In the previous third and fouth quarterly status reports 2019, the sysctlinfo
interface and an extension to improve the sysctlbyname() syscall were described,
they can access to the sysctl MIB and pass the properties of an object to the
userland, but both are quite low level and kernel related.
</p>
<p>The sysctlmibinfo2 library provides an API to explore the sysctl MIB, to convert
an object name in its corresponding Object Identifier and to find an object to
get its properties, therefore it is useful to handle an object correctly and to
build a sysctl-like utility.
</p>
<p>Primarily sysctlmibinfo2 wraps the low level interface to provide an easy API,
some example: sysctlmif_desc() retrieves the description of an object,
sysctlmif_kind() gets the type (string, integer, etc) and sysctlmif_fmt()
specifies the format (an integer could represent a deciKelvin, milliKelvin,
etc), then it is possible to print properly an object value.
</p>
<p>Moreover sysctlmibinfo2 provides a high level API: a struct sysctlmif_object
definition and functions to build data structures of objects.
Example, let's say we want to manage the sound system,
sysctlmif_grouplistbyname("hw.snd") returns the list of the Sound Driver
objects and sysctlmif_treebyname("dev.pcm") returns a tree where "dev.pcm" is
the root node and each subtree represents an audio device.
</p>
<p>Obviously sysctlmibinfo2 benefits of the features of sysctlinfo: handles OIDs
up to CTL_MAXNAME levels, supports capability mode, can seek an object by its
name (avoiding to explore the MIB just to find the corresponding OID), gets all
info about an object in a time, manages a name with a NULL level or expanded
with an input for the sysctl handler.
</p>
<p>The library can be installed via the devel/libsysctlmibinfo2 port, a manual page
and examples in the Public Domain are available for getting started your
projects.
</p></body></project>
<project cat='third'>
<title>pot and the nomad pot driver</title>
<links>
<url href='https://pot.pizzamig.dev'>pot project</url>
<url href='https://github.com/pizzamig/pot'>pot on github</url>
<url href='https://github.com/trivago/nomad-pot-driver'>Nomad pot driver</url>
<url href='https://github.com/pizzamig/minipot'>minipot</url>
</links>
<contact>
<person>
<name>Luca Pizzamiglio</name>
<email>pizzamig@FreeBSD.org</email>
</person>
<person>
<name>Esteban Barrios</name>
<email>esteban.barrios@trivago.com</email>
</person>
</contact>
<body><p>An initial effort to write proper documentation and guides for the pot project has started. The documentation, even if incomplete, is available at <a href='https://pot.pizzamig.dev'>here</a>. A <a href='https://pot.pizzamig.dev/FAQ/'>F.A.Q.</a> page is available and waiting for users to submit their questions.
</p>
<p>During the last quarter, some bugs were reported on pot and on the nomad-pot-driver. Both projects released a new bug fix version.
Many thanks to 'grembo' and 'Crest' that reported issues, tested and tried our solutions.<br />
Thanks also to Mateusz (0mp) for his Pull Requests!
</p>
<p>pot will have a new release soon (0.11.0), focused on network:
</p>
<ul>
<li><p>network stack support: ipv4 only, ipv6 only, dual stack.
</p></li>
<li><p>flexible network setup for alias: adding the ability to use an arbitrary network setup for alias network type
</p>
</li></ul>
Contributions are welcome! Label "good first issue" has been added to issues to invite newcomers to contribute to the project!
</body></project>
<project cat='third'>
<title>NomadBSD</title>
<links>
<url href='https://www.nomadbsd.org/'>NomadBSD Website</url>
<url href='https://www.github.com/NomadBSD/NomadBSD'>NomadBSD Github</url>
<url href='https://forum.NomadBSD.org/'>NomadBSD Forum</url>
</links>
<contact>
<person>
<name>NomadBSD Team</name>
<email>info@NomadBSD.org</email>
</person>
</contact>
<body><p>NomadBSD is a persistent live system for USB flash drives, based on FreeBSD.
Together with automatic hardware detection and setup, it is configured to be
used as a desktop system that works out of the box, but can also be used for
data recovery, for educational purposes, or testing FreeBSD's hardware
compatibility.
</p>
<p>In March we released a new minor version 1.3.1 which improves the configuration
of the network interfaces, fixed some bugs and added nomadbsd-chusr and
nomadbsd-sysinfo. Further some new features found their way into the release.
</p>
<p>Some days later the channel explainingcomputers on YouTube released a review video of
NomadBSD. The explainingcomputers has almost 600,000 followers and the review was positive
so we saw the highest peak in downloads ever! Along with it came a lot of people looking for
help on our mailing list and on Twitter so we decided to set up a new support forum.
</p>
<p>We are looking for people to help the project. Help is much appreciated in all areas:
</p>
<ul>
<li><p>Translation of program interfaces
</p></li>
<li><p>Design artwork
</p></li>
<li><p>Programming new tools, extend existing ones
</p></li>
<li><p>Tests and Bug reports / UX and feature suggestions
</p></li>
<li><p>Mirrors outside of Europe
</p>
</li></ul>
Open tasks:
<ul>
<li><p>Support installation on disk partitions and add a partition editor GUI.
</p></li>
<li><p>Complete disk encryption
</p></li>
<li><p>Add a user-friendly network manager
</p></li></ul>
</body></project>
<category>
<name>team</name>
<description>&os; Team Reports</description>
<p>Entries from the various official and semi-official teams,
as found in the <a href="&enbase;/administration.html">Administration
Page</a>.</p>
</category>
<category>
<name>proj</name>
<description>Projects</description>
<p>Projects that span multiple categories, from the kernel and userspace
to the Ports Collection or external projects.</p>
</category>
<category>
<name>kern</name>
<description>Kernel</description>
<p>Updates to kernel subsystems/features, driver support,
filesystems, and more.</p>
</category>
<category>
<name>arch</name>
<description>Architectures</description>
<p>Updating platform-specific features and bringing in support
for new hardware platforms.</p>.
</category>
<category>
<name>bin</name>
<description>Userland Programs</description>
<p>Changes affecting the base system and programs in it.</p>
</category>
<category>
<name>ports</name>
<description>Ports</description>
<p>Changes affecting the Ports Collection, whether sweeping
changes that touch most of the tree, or individual ports
themselves.</p>
</category>
<category>
<name>doc</name>
<description>Documentation</description>
<p>Noteworthy changes in the documentation tree, in manpages, or in
external books/documents.</p>
</category>
<category>
<name>third</name>
<description>Third-Party Projects</description>
<p>Many projects build upon &os; or incorporate components of
&os; into their project. As these projects may be of interest
to the broader &os; community, we sometimes include brief
updates submitted by these projects in our quarterly report.
The &os; project makes no representation as to the accuracy or
veracity of any claims in these submissions.</p>
</category>
</report>
|
