[Bug 248899] shutdown -p now cannot power down cleanly on 13.0-CURRENT r364441

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

Bug ID: 248899
   Summary: shutdown -p now cannot power down cleanly on
13.0-CURRENT r364441
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: i...@amail.plala.or.jp

I'm using dell studio 1558 laptop machine.
On 13.0-CURRENT r364441, 'shutdown -p now' makes sleep after shutdown, not
powered off. 
It can power off normally on 12.1-RELEASE-p8.

-- 
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 248008] i386 system can hang with many processes sleeping on btalloc post base r358097

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

Rick Macklem  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|rmack...@freebsd.org
 Status|Open|In Progress

--- Comment #17 from Rick Macklem  ---
I have committed the first attachment patch to head.
I will leave this PR open for a while, in case markj@ chooses
to commit a different 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 248008] i386 system can hang with many processes sleeping on btalloc post base r358097

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

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

Author: rmacklem
Date: Tue Aug 25 00:58:14 UTC 2020
New revision: 364744
URL: https://svnweb.freebsd.org/changeset/base/364744

Log:
  Fix hangs with processes stuck sleeping on btalloc on i386.

  r358097 introduced a problem for i386, where kernel builds will
intermittently
  get hung, typically with many processes sleeping on "btalloc".
  I know nothing about VM, but received assistance from rlibby@ and markj@.

  rlibby@ stated the following:
 It looks like the problem is that
 for systems that do not have UMA_MD_SMALL_ALLOC, we do
 uma_zone_set_allocf(vmem_bt_zone, vmem_bt_alloc);
 but we haven't set an appropriate free function.  This is probably why
 UMA_ZONE_NOFREE was originally there.  When NOFREE was removed, it was
 appropriate for systems with uma_small_alloc.

 So by default we get page_free as our free function.  That calls
 kmem_free, which calls vmem_free ... but we do our allocs with
 vmem_xalloc.  I'm not positive, but I think the problem is that in
 effect we vmem_xalloc -> vmem_free, not vmem_xfree.

 Three possible fixes:
  1: The one you tested, but this is not best for systems with
 uma_small_alloc.
  2: Pass UMA_ZONE_NOFREE conditional on UMA_MD_SMALL_ALLOC.
  3: Actually provide an appropriate vmem_bt_free function.

 I think we should just do option 2 with a comment, it's simple and it's
 what we used to do.  I'm not sure how much benefit we would see from
 option 3, but it's more work.

  This patch implements #2. I haven't done a comment, since I don't know
  what the problem is.

  markj@ noted the following:
 I think the suggested patch is ok, but not for the reason stated.
 On platforms without a direct map the problem is:
 to allocate btags we need a slab,
 and to allocate a slab we need to map a page, and to map a page we need
 to allocate btags.

 We handle this recursion using a custom slab allocator which specifies
 M_USE_RESERVE, allowing it to dip into a reserve of free btags.
 Because the returned slab can be used to keep the reserve populated,
 this ensures that there are always enough free btags available to
 handle the recursion.

 UMA_ZONE_NOFREE ensures that we never reclaim free slabs from the zone.
 However, when it was removed, an apparent bug in UMA was exposed:
 keg_drain() ignores the reservation set by uma_zone_reserve()
 in vmem_startup().
 So under memory pressure we reclaim the free btags that are needed to
 break the recursion.
 That's why adding _NOFREE back fixes the problem: it disables the
 reclamation.

 We could perhaps fix it more cleverly, by modifying keg_drain() to always
 leave uk_reserve slabs available.

  markj@'s initial patch failed testing, so committing this patch was agreed
  upon as the interim solution.
  Either rlibby@ or markj@ might choose to add a comment to it.

  PR:   248008
  Reviewed by:  rlibby, markj

Changes:
  head/sys/kern/subr_vmem.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 248763] Kernel built with LLVM 11 doesn't boot on powerpc64

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

Brandon Bergren  changed:

   What|Removed |Added

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

--- Comment #4 from Brandon Bergren  ---
Fixed by the updated LLVM toolchain.

-- 
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 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #12 from Michael Osipov  ---
No ticket, certificate. Typo.

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


[Bug 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #11 from Michael Osipov  ---
(In reply to Kyle Evans from comment #10)

Correct. I would start populate blacklist first and then generate links. Care
must be taken if  diverge, say you have n certs in blacklist with the
same subject hash, great care must be taken when creating links that the
correct certs is excluded from linking
(https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_load_verify_locations.html).
I think the general approach is to calculate a hash on the ASN.1 DER-encoded
form of the ticket which will be truly unique.

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


[Bug 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #10 from Kyle Evans  ---
(In reply to Michael Osipov from comment #9)

Ah, OK, I see what you mean. So really, `certctl blacklist` should probably
just be adding to /usr/share/certs/blacklisted and pulling any
newly-blacklisted certs from /etc/ssl/certs. create_blacklisted goes away and
create_trusted_link needs to be revised to figure out from
/usr/share/certs/blacklisted if the link should be installed or not, if I
understand correctly.

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


[Bug 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #9 from Michael Osipov  ---
(In reply to Kyle Evans from comment #8)

Not even that. The origin c_rehash is not aware of blacklists, only CRLs. So
the idea behind a blacklist is that you exclude specific certs from installing.
This means that if a cert exists in the blackist and in the source, the hash
link is never created (or removed) is /etc/ssl/certs. They must be skipped.
When the link is established, OpenSSL assumes that you trust that entity. If
you don't want to work with blacklists, use CRL. I don't see a reason to copy
with the original name. What benefit should that give?

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


[Bug 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #8 from Kyle Evans  ---
(In reply to Michael Osipov from comment #6)

> * create_blacklisted() is completely ill-designed for several reasons:
> ** When processing all links must be purged first
> ** Blacklisted certs should not be linked at all
> ** using .r is wrong because the r suffix is solely reserved for 
> CRLs. Look into c_rehash: elsif($hdr eq "X509 CRL") {$is_crl = 1;..}

They shouldn't be linked, so they should probably just retain their original
name and get copied in rather than messing with . notation, right?

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


[Bug 248715] dhclient: prepend domain-name-servers in dhclient.conf 'replaces' dhcpd provided value

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

--- Comment #2 from Dmitry Afanasiev  ---
I'm not checked all prepend options, but option "prepend domain-name" works
propely.

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


COVID 19'un Sektörlere ve Mali Tablolara Etkisi

2020-08-24 Thread Türkiye Sermaye Piyasaları Birliği

TSPB Birlikte Eğitim Mesleki Gelişim Eğitimleri





Blteni Daha İyi Grntlemek İin Tıklayın
[http://track-7.my-email-sender.com/0110D2389707|10109990485b4d55f5b11034a73625947252|01115490|0101469|00112514.html]TSPB
Birlikte Eğitim Mesleki Gelişim Eğitimleri
"COVID 19'un Sektrlere ve Mali Tablolara Etkisi"



Online Eğitim"Zoom"uygulaması zerinden
gerekleştirilecektir.

Eğitimin 25 kişilik kontenjanı bulunmaktadır.

Başvurularını gerekleştirilen katılımcılara online eğitime
giriş iin gerekli bilgiler iletilecektir.

Başvuru iin: www.tspb.org.tr
[http://track-7.my-email-sender.com/0011L2389707|01115490|110022069|1001T.html]


yelik ve başvurularınızla ilgili sorularınız iin:
info@birlikteeğitim.org [mailto:info@birlikteeğitim.org]
ve ya aşağıdaki telefon numarasından bize ulaşabilirsiniz.

Eğitmen: Prof. Dr. Barış Sipahi-Marmara niversitesi-İşletme
Fakltesi

Eğitim Tarihi: 21 Eyll 2020
Eğitim Sresi:  Gn
Ders Saati: 13:30-17:30

Eğitim creti: 200 TL (KDV dahil, kişi başı)

Eğitim Yeri: Online Eğitim-Zoom

Başvuru: www.tspb.org.tr
[http://track-7.my-email-sender.com/1010L2389707|01105490|011122069|0111T.html]


TSPB Birlikte Eğitim
Bykdere Caddesi No: 173 1.Levent Plaza A Blok Kat4
Şişli-İstanbul
Telefon: 0212 280 85 67
i...@birlikteegitim.org [mailto:i...@birlikteegitim.org]
www.tspb.org.tr
[http://track-7.my-email-sender.com/1001L2389707|00115490|01015892|0111T.html]



Pandemi srecinin sektrlere yansıması nedir?

Hangi sektr olumlu etkilendi?

Hangi sektr olumsuz etkilendi?

Sektrel değişim ve beklentileri nasıl yorumlamalıyım?

Merak ettiğiniz soruların cevabını eğitimimizde bulacaksınız.


21 Eyll 2020 tarihinde "COVID 19'un Sektrlere ve Mali Tablolara
Etkisi" online eğitimimize bekliyoruz.

EĞİTİM KONULARI

Dayanıklı Tketim Malları Sektr Mevcut Durumu ve
COVID'in Mevcut Duruma Etkileri

Tekstil ve Konfeksiyon Sektr Mevcut Durumu ve COVID'in Mevcut
Duruma Etkileri

Otomotiv Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

İnşaat Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

Turizm Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

Gıda Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

Perakende Sektr Mevcut Durumu ve COVID'in Mevcut Duruma
Etkileri

Tarım Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

Ulaşım Sektr Mevcut Durumu ve COVID'in Mevcut Duruma Etkileri

Endeksler

Sanayi retim Endeksi

Sektrel Gven Endeksi

Reel Kesim Gven Endeksi

İmalat Sanayi Kapasite Kullanım Oranları

Bu e-posta tarafınıza TSPB tarafından oluşturulan ye
veritabanına kayıtlı olduğunuz iin gnderilmiştir.Beni bu
listeden ıkar
[http://track-7.my-email-sender.com/1101U2389707|10109990485b4d55f5b11034a73625947252|1000469|10005490.html]

___
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 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #7 from Kyle Evans  ---
(In reply to Michael Osipov from comment #6

D'oh! Thanks, will address some of this tonight.

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


[Bug 248869] e1000: unsolicited promisc mode during init

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

Mark Linimon  changed:

   What|Removed |Added

   Keywords||IntelNetworking, regression
   Assignee|b...@freebsd.org|n...@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 248865] rc script in /usr/local/etc/rc.d/ may be ignored

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

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|r...@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 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #6 from Michael Osipov  ---
Went through the given diff, there are still issues with it:
* serial should be turned into decimal to avoid confusion
* create_blacklisted() is completely ill-designed for several reasons:
** When processing all links must be purged first
** Blacklisted certs should not be linked at all
** using .r is wrong because the r suffix is solely reserved for
CRLs. Look into c_rehash: elsif($hdr eq "X509 CRL") {$is_crl = 1;..}

BUT the rehashing does work:
> root@deblndw011x:/etc/ssl/certs
> # ll | grep 8dc03e53
> lrwxr-xr-x  1 root  wheel  52 2020-08-24 09:54 8dc03e53.0@ -> 
> ../../../usr/local/etc/ssl/certs/siemens-cert-14.crt
> lrwxr-xr-x  1 root  wheel  52 2020-08-24 09:54 8dc03e53.1@ -> 
> ../../../usr/local/etc/ssl/certs/siemens-cert-15.crt
> root@deblndw011x:/etc/ssl/certs
> # certctl list | grep "Siemens Internet CA V1.0"
> 8dc03e53.0  Siemens Internet CA V1.0

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


[Bug 246614] certctl(8) silently overwrites certs with same subjects

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

--- Comment #5 from Michael Osipov  ---
(In reply to Kyle Evans from comment #4)

Looking through. Note that I do not have access to Phabricator anymore because
login via Google is rejected. Already notified the Phabricator admin.

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


[Bug 248869] e1000: unsolicited promisc mode during init

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

Franco Fichtner  changed:

   What|Removed |Added

 Attachment #217479|0   |1
   is patch||
 Attachment #217479|application/mbox|text/plain
  mime type||

-- 
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 248869] e1000: unsolicited promisc mode during init

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

Bug ID: 248869
   Summary: e1000: unsolicited promisc mode during init
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: fra...@opnsense.org

Created attachment 217479
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=217479=edit
flags fix

Hi,

The iflib rewrite forced the promisc flag but it was not reported to the
system.  Noticed on a stock VM that went into unsolicited promisc mode when
dhclient was started during bootup.

This also affects CURRENT and is present since 12.0, but marking this as a
12.1-RELEASE issue.

Patch is attached to restore the previous behaviour.


Cheers,
Franco

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