Re: hibernation — does it work for you?
Yes - works for me, reliably, on a Dell XPS13 L322X - using F27/28. Was a bit hickuppy in F27, but haven't had any issues with F28 that I can recall. On Wed, Oct 3, 2018 at 5:39 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > We have had a long discussion about hibernate (suspend to disk) > being unreliable. But there seems to be no hard data. Let's gather > some! > > If you perform hibernation (systemctl hibernate, or the equivalent > through the GUI), does _your_ system suspend and resume correctly? > > Note: I'm not talking about the user-space configuration issues > (resume= not set on the kernel command line, no swap, swap encrypted > with temporary keys, whatever), but only about any potential kernel > driver issues. > > My stats (with various version of Fedora): > – thinkpad x1c 4th gen: no issues > – thinkpad x1c 3rd gen: no issues > – thinkpad x230: no issues > – chromebook 2013 model: spurious wakeups after the lid was closed > – thinkpad t50: no issues (*) > – hp pavilion dv7: no issues (*) > > So in my own experience, s2d usually works. Does it work for you? > > Zbyszek > > (*) on this older hardware is where I used hibernation a lot, > on the newer ones, not that much. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
Does not work on Thinkpad x270 with F28 - kernel 4.18.10-200. Ended up in terminal with cursor blinking (last thing I saw on start was resuming from hibernation). I did manual reset after 20 minutes. On 3.10.2018 17:38, Zbigniew Jędrzejewski-Szmek wrote: We have had a long discussion about hibernate (suspend to disk) being unreliable. But there seems to be no hard data. Let's gather some! If you perform hibernation (systemctl hibernate, or the equivalent through the GUI), does _your_ system suspend and resume correctly? Note: I'm not talking about the user-space configuration issues (resume= not set on the kernel command line, no swap, swap encrypted with temporary keys, whatever), but only about any potential kernel driver issues. My stats (with various version of Fedora): – thinkpad x1c 4th gen: no issues – thinkpad x1c 3rd gen: no issues – thinkpad x230: no issues – chromebook 2013 model: spurious wakeups after the lid was closed – thinkpad t50: no issues (*) – hp pavilion dv7: no issues (*) So in my own experience, s2d usually works. Does it work for you? Zbyszek (*) on this older hardware is where I used hibernation a lot, on the newer ones, not that much. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
On Fri, Oct 5, 2018 at 10:20 PM Lennart Poettering wrote: > I have thus prepared this a few days ago: > > https://github.com/systemd/systemd/pull/10244 This is great, thank you. So, any idea why they picked 1M? Are there typical apps that require > really that many? > I've emailed Zebediah Figura, the esync author. I asked him to either get back to me and I'll resend his reply here, or to comment in your pull request. Hopefully he can tell us what his process was for picking the 1M value. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
Maybe it will be also good to look at the SteamOS distribution and what limits they are using. On 8.10.2018 10:53, Kamil Paral wrote: On Fri, Oct 5, 2018 at 10:20 PM Lennart Poettering mailto:mzerq...@0pointer.de>> wrote: I have thus prepared this a few days ago: https://github.com/systemd/systemd/pull/10244 This is great, thank you. So, any idea why they picked 1M? Are there typical apps that require really that many? I've emailed Zebediah Figura, the esync author. I asked him to either get back to me and I'll resend his reply here, or to comment in your pull request. Hopefully he can tell us what his process was for picking the 1M value. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
On Mon, Oct 8, 2018 at 11:09 AM Michal Konečný wrote: > Maybe it will be also good to look at the SteamOS distribution and what > limits they are using. > According to the proton document [1], SteamOS also has an increased fileno hard limit. I haven't verified the actual value, but they probably just inherit it from Debian. And on SteamOS they really wouldn't need to go lower than on Debian, it's a gaming-only OS. [1] https://github.com/ValveSoftware/Proton/blob/proton_3.7/PREREQS.md#fd-limit-requirements ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Thu, Oct 04, 2018 at 08:33:13AM -0400, Sam Varshavchik wrote: > I tried to enable suspension it works > maybe once or twice, but then eventually the laptop fails to come > out of suspended state no matter what, so I end up power-cycling it, > then turning off suspension in power management, and only have it > turn the display off. That's most likely some kernel driver and/or firmware issue. With suspend, the userspace just issues the order, and the kernel does the rest. > Hibernation never worked, to my recollection. Just tried to > hibernate this laptop. The display flickered a few times, the > laptop's speaker made a few reassuring beeps, then the whole thing > turned itself off. The next boot was a normal boot. Normal grub > menu, normal boot. No evidence of anything being hibernated. > Probably a userspace issue, but I have no idea where to look. That sounds as if the 'resume=' parameter is missing from the kernel command line. The system then just boots normally, which matches the symptoms you describe. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Thu, Oct 04, 2018 at 04:47:13PM +0200, mcatanz...@gnome.org wrote: > On Wed, Oct 3, 2018 at 5:38 PM, Zbigniew Jędrzejewski-Szmek > wrote: > >Note: I'm not talking about the user-space configuration issues > >(resume= not set on the kernel command line, no swap, swap encrypted > >with temporary keys, whatever), but only about any potential kernel > >driver issues. > > Well "whatever" is a big deal here, we need to know exactly what is > expected to work and what not before we can test this, or we'll > provide you with false reports that it's broken. Let's define "works" as "good enough for you as a user for whatever you use the machine for". > A default install of Fedora with encryption enabled creates swap on > encrypted LVM. Is that expected to work? I'm not planning to > repartition my computer to test this and it's maybe not worth > arguing about if that's not expected to work. Yes, I have such setup. Usually the root partition and the swap partition are very similar. So if dracut is able to figure out how to decrypt and mount your root partition, it can do the same with swap. > Also, don't forget secure boot, kinda a big deal Yeah, secure boot kills the whole idea. One of the reason why I don't use secure boot. I hope the kernel reports hibernation as impossible if secure boot is enabled. It should, and if it doesn't we need to add a check in systemd. It would be great if somebody with SB enabled could say what /sys/power/state and /sys/power/disk contain. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Thu, Oct 04, 2018 at 08:35:20PM +0200, Timothée Floure wrote: > > We have had a long discussion about hibernate (suspend to disk) > > being unreliable. But there seems to be no hard data. Let's gather > > some! > > I might have missed something, but can you link me the "long discussion"? Do > we > have a page on the subject somewhere on the wiki? https://lists.fedoraproject.org/archives/list/desk...@lists.fedoraproject.org/thread/AUHETMQF6VIL6SG4VZXA4GQB43BAW7NJ/ "Disable (or make configurable and default to off) suspend-then-hibernate behavior in GNOME-3.30" https://lists.fedoraproject.org/archives/list/desk...@lists.fedoraproject.org/thread/TLTA6HAYJWQYHV3ZHFXUIXM4IJVWBEJJ/ "Disabling kernel's hibernate support by default, allow re-enabling it with a kernel cmdline option" https://lists.fedoraproject.org/archives/list/desk...@lists.fedoraproject.org/thread/YOTPDRPY6ZTFGVCPMFWGPA3KRDNFHLOD/ "system now hibernates automatically 3 hours after suspend ?" (note that those are cross-posted to kernel@fp.o, sometimes fedora-devel@fp.o, so it's a bit a thicket to navigate.) > > If you perform hibernation (systemctl hibernate, or the equivalent > > through the GUI), does _your_ system suspend and resume correctly? > > Works perfectly on my T440s :-) Cool. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Sat, Oct 06, 2018 at 04:19:19PM -, Karlis Kalviskis wrote: > * Panasonic Toughbook CF-19 with kernel 4.18.11-200.fc28.i686 _DOES NOT_ work > as expected: > > - it pretends to save hibernation data and switches off. > - when the computer starts, it begins to read the hibernation data, reboots > and start as normal power-on. > > Some funny data: > # lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 465,8G 0 disk > [..] > ├─sda4 8:40 3,9G 0 part [SWAP] > [..] > > # swapon --show > NAME TYPE SIZE USED PRIO > /dev/sda4 partition 2G 0B -2 > > Something wrong with size information Interesting. What does 'sudo file -Ls /dev/sda4' show? Also, looking at the partition table, does the 3.9GB size match the space until the next partition? Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Monday, 08 October 2018 at 12:03, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Oct 04, 2018 at 04:47:13PM +0200, mcatanz...@gnome.org wrote: [...] > > Also, don't forget secure boot, kinda a big deal > Yeah, secure boot kills the whole idea. One of the reason why I don't > use secure boot. I hope the kernel reports hibernation as impossible > if secure boot is enabled. It should, and if it doesn't we need to add > a check in systemd. It would be great if somebody with SB enabled could > say what /sys/power/state and /sys/power/disk contain. This is on Fedora 28: $ dmesg |grep secureboot [0.00] secureboot: Secure boot enabled $ cat /sys/power/state freeze mem $ cat /sys/power/disk [disabled] Regards, Dominik -- Fedora https://getfedora.org | RPMFusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you: quick summary
Various people replied, both here and on reddit [1]. Thank you all! Short summary: works (possibly with minor glitches): 27 works but with occasional regressions in some kernel versions: 3 unusable: 10 Results in tabular form: zbyszek: Thinkpad x1c 4th gen: no issues zbyszek: Thinkpad x1c 3rd gen: no issues zbyszek: Thinkpad x230: no issues zbyszek: Chromebook 2013 model: spurious wakeups after the lid was closed zbyszek: Thinkpad t50: no issues zbyszek: HP Pavilion dv7: no issues Artur Iwicki: Panasonic Toughbook CF-29: works fine, regressions (hib aborts) with some kernel versions Thinkpad X220: usually works fine, but sometimes long time to hibernate (8 minutes), long time to wake up Tony Nelson: Acer Aspire E15 ES1-512-P9GT: fine, but regressions (no poweroff) with some kernel versions Akarshan Biswas: Acer Aspire E15 E5-523-98R2: DOESN'T WORK, suspend also broken Tom Hughes: Dell XPS 13 9360: works Björn Persson: Clevo W25CEW: resume fails, boots normally instead Alexander Mikhaylenko: ASUS P53E: works, but power indicator stops reporting status until cable is replugged Jani Juhani Sinervo: Lenovo Z50-70: BROKEN (network adapter, poweroff don't work properly) Dell XPS 13 L322X: works Michiel Bodewes: HP pavilion g15-cx0953nd: UNRELIABLE RESUME hard-reset required (dual-gpu with nvidia prop. driver) Kamil Paral: Thinkpads R61, X220, T450s, T480s: OK Thinkpads T500: OK, but rare issues with CPU lockup Intel desktop with Gigabyte GA-Z87-D3HP: DRIVER PROBLEMS (maybe fixed with newer kernel versions) Juha Nikkanen: Asus Sabertooth 990 FX Rel 1 with bios 1604 and 8150FX CP: SOMETIMES WORKS Enno Zickle: Thinkpad T430: works Timothée Floure: Thinkpad T440s: works Kevin Fenzi: Yoga 920: works (lock track in dmesg from ath10k) Karlis Kalviski: Dell Inspiron 1525: works Panasonic Toughbook CF-19: NO RESUME (swap partition size screwup) Jan De Luyck: Dell XPS13 L322X: works Michal Konečný: Thinkpad x270: NO RESUME (terminal with cursor blinking) Nom_Ent: Lenovo Thinkpad T420: works (arch) YouNeverWalkAlone: ThinkPad E470: BROKEN (arch, using ZZZ) pr0ghead: Gigabyte GA-Z170X-Gaming 7 mainboard with an Intel Core i5-6600K using its IGP: STOPPED WORKING (kernel 4.17- is fine) Ben496: Asus Z97i-plus mobo: works (arch) Asus Zenbook NX500J: works (debian) elniko77: Lenovo t470: works yrro: Lenono P50: works (debian) Toshiba X30: works (debian) Toshiba X40: works (debian) Samsung Q45: works (debian) [If no distribution is mentioned, Fedora is implied. I included the names of the reporters because otherwise it'd be hard to find the report. The names are public on the posts anyway. I ignored the reports which don't include the hardware information.] [1] https://www.reddit.com/r/linux/comments/9l3qoe/hibernation_does_it_work_for_you_fedora_deve_listl/ (thanks to mattdm for forwarding the fedora-devel thread to reddit) Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: hibernation — does it work for you?
On Mon, Oct 08, 2018 at 12:42:08PM +0200, Dominik 'Rathann' Mierzejewski wrote: > On Monday, 08 October 2018 at 12:03, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Oct 04, 2018 at 04:47:13PM +0200, mcatanz...@gnome.org wrote: > [...] > > > Also, don't forget secure boot, kinda a big deal > > Yeah, secure boot kills the whole idea. One of the reason why I don't > > use secure boot. I hope the kernel reports hibernation as impossible > > if secure boot is enabled. It should, and if it doesn't we need to add > > a check in systemd. It would be great if somebody with SB enabled could > > say what /sys/power/state and /sys/power/disk contain. > > This is on Fedora 28: > $ dmesg |grep secureboot > [0.00] secureboot: Secure boot enabled > $ cat /sys/power/state > freeze mem > $ cat /sys/power/disk > [disabled] Thanks! Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Schedule for Monday's FESCo Meeting (2018-10-08)
Following is the list of topics that will be discussed in the FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2018-10-08 15:00 UTC' Links to all issues to be discussed can be found at: https://pagure.io/fesco/report/meeting_agenda = Followups = #topic #1974 Problematic blocker for F29: dnf 'offline' module tracking .fesco 1974 https://pagure.io/fesco/issue/1974 = Open Floor = For more complete details, please visit each individual issue. The report of the agenda items can be found at https://pagure.io/fesco/report/meeting_agenda If you would like to add something to this agenda, you can reply to this e-mail, file a new issue at https://pagure.io/fesco, e-mail me directly, or bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: EXTERNAL: Re: hibernation — does it work for you?
On 10/8/18 4:16 AM, Michal Konečný wrote: > Does not work on Thinkpad x270 with F28 - kernel 4.18.10-200. Nor does it work on Thinkpad x260 with F28 - same kernel > > Ended up in terminal with cursor blinking (last thing I saw on start > was resuming from hibernation). I did manual reset after 20 minutes. > > On 3.10.2018 17:38, Zbigniew Jędrzejewski-Szmek wrote: >> We have had a long discussion about hibernate (suspend to disk) >> being unreliable. But there seems to be no hard data. Let's gather >> some! >> >> If you perform hibernation (systemctl hibernate, or the equivalent >> through the GUI), does _your_ system suspend and resume correctly? >> >> Note: I'm not talking about the user-space configuration issues >> (resume= not set on the kernel command line, no swap, swap encrypted >> with temporary keys, whatever), but only about any potential kernel >> driver issues. >> >> My stats (with various version of Fedora): >> – thinkpad x1c 4th gen: no issues >> – thinkpad x1c 3rd gen: no issues >> – thinkpad x230: no issues >> – chromebook 2013 model: spurious wakeups after the lid was closed >> – thinkpad t50: no issues (*) >> – hp pavilion dv7: no issues (*) >> >> So in my own experience, s2d usually works. Does it work for you? >> >> Zbyszek >> >> (*) on this older hardware is where I used hibernation a lot, >> on the newer ones, not that much. >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Roger Wells, P.E. leidos 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@leidos.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora Atomic Host Two Week Release Announcement: 28.20181007.0
A new Fedora Atomic Host update is available via an OSTree update: Version: 28.20181007.0 Commit(x86_64): 8df48fa2e70ad1952153ae00edbba08ed18b53c3d4095a22985d1085f5203ac6 Commit(aarch64): 6b8d55e59750cfe8e490dbfa63ab12ccdb0a231a4d58e1b074793dddb6c49648 Commit(ppc64le): 4a95f167ee4063556daf59e13b85f7d84fb1073db4150c8f3dd6a4a36c80523f We are releasing images from multiple architectures but please note that x86_64 architecture is the only one that undergoes automated testing at this time. Existing systems can be upgraded in place via e.g. `atomic host upgrade`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Alternatively, image artifacts can be found at the following links: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20181007.0.iso https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20181007.0.iso https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.qcow2 https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.raw.xz https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-libvirt.box https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-virtualbox.box https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20181007.0.iso Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM For direct download, the "latest" targets are always available here: x86_64: https://getfedora.org/atomic_qcow2_x86_64_latest https://getfedora.org/atomic_raw_x86_64_latest https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest https://getfedora.org/atomic_dvd_ostree_x86_64_latest aarch64: https://getfedora.org/atomic_qcow2_aarch64_latest https://getfedora.org/atomic_raw_aarch64_latest https://getfedora.org/atomic_dvd_ostree_aarch64_latest ppc64le: https://getfedora.org/atomic_qcow2_ppc64le_latest https://getfedora.org/atomic_raw_ppc64le_latest https://getfedora.org/atomic_dvd_ostree_ppc64le_latest Filename fetching URLs are available here: x86_64: https://getfedora.org/atomic_qcow2_x86_64_latest_filename https://getfedora.org/atomic_raw_x86_64_latest_filename https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename aarch64: https://getfedora.org/atomic_qcow2_aarch64_latest_filename https://getfedora.org/atomic_raw_aarch64_latest_filename https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename ppc64le: https://getfedora.org/atomic_qcow2_ppc64le_latest_filename https://getfedora.org/atomic_raw_ppc64le_latest_filename https://getfedora.org/atomic_dvd_ostree_ppc64le_latest_filenam
Re: poppler soname bump in rawhide
Il giorno mar 14 ago 2018 alle 2:31, Marek Kasik ha scritto: Hi, I'm going to rebase poppler in rawhide to poppler-0.67.0 now. There are several API changes and soname bump of the base library libpoppler.so.*. I've checked all packages which depend on the libpoppler.so.* and have backported/prepared fixes to reflect poppler's API changes. Unfortunately, libreoffice does not build currently (#1615616). But I've decided to push the rebase though because branching will happen today and I could not do chain build after that for F29. Btw, if your package use the unstable API (headers from poppler-devel), could you consider to change it to use a stable API (glib, qt, C++)? Hi Marek upstream developer of the package I maintain (extractpdfmark) has just opened a merge request that would allow him to use the stable API: https://gitlab.freedesktop.org/poppler/poppler/merge_requests/75 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
taking over some of fale's packages
Hi, As fale has orphaned packages ( https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TTRKFTADCEHAJSZ55YXIPT3DOZY5RTYW/ ) I would like to take over rubygem-asciidoctor-pdf and some of its dependencies. I've opened https://pagure.io/releng/issue/7855 Please let me know if there are objections. Regards, François ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora Atomic Host Two Week Release Announcement: 28.20181007.0
On Mon, Oct 8, 2018 at 7:04 PM wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 28.20181007.0 > Commit(x86_64): > 8df48fa2e70ad1952153ae00edbba08ed18b53c3d4095a22985d1085f5203ac6 > Commit(aarch64): > 6b8d55e59750cfe8e490dbfa63ab12ccdb0a231a4d58e1b074793dddb6c49648 > Commit(ppc64le): > 4a95f167ee4063556daf59e13b85f7d84fb1073db4150c8f3dd6a4a36c80523f > > > We are releasing images from multiple architectures but please note > that x86_64 architecture is the only one that undergoes automated > testing at this time. > > Existing systems can be upgraded in place via e.g. `atomic host upgrade`. > > Corresponding image media for new installations can be downloaded from: > > https://getfedora.org/en/atomic/download/ > > Alternatively, image artifacts can be found at the following links: > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.qcow2 > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.raw.xz > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20181007.0.iso > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.qcow2 > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.raw.xz > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20181007.0.iso > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.qcow2 > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.raw.xz > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-libvirt.box > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-virtualbox.box > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20181007.0.iso > > Respective signed CHECKSUM files can be found here: > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM > > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM > > For direct download, the "latest" targets are always available here: > x86_64: > https://getfedora.org/atomic_qcow2_x86_64_latest > https://getfedora.org/atomic_raw_x86_64_latest > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest > https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest > https://getfedora.org/atomic_dvd_ostree_x86_64_latest > > aarch64: > https://getfedora.org/atomic_qcow2_aarch64_latest > https://getfedora.org/atomic_raw_aarch64_latest > https://getfedora.org/atomic_dvd_ostree_aarch64_latest > > ppc64le: > https://getfedora.org/atomic_qcow2_ppc64le_latest > https://getfedora.org/atomic_raw_ppc64le_latest > https://getfedora.org/atomic_dvd_ostree_ppc64le_latest > > Filename fetching URLs are available here: > x86_64: > https://getfedora.org/atomic_qcow2_x86_64_latest_filename > https://getfedora.org/atomic_raw_x86_64_latest_filename > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename > https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename > https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename > > aarch64: > https://getfedora.org/atomic_qcow2_aarch64_latest_filename > https://getfedora.org/atomic_raw_aarch64_latest_filename > https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
Re: libunbound SONAME bump
Unbound is rebuilt on master. Please bump and rebuild dependent packages. On 10/02/2018 02:15 PM, Petr Mensik wrote: > Hi! > > I am planning to push new unbound 1.8.0 into rawhide. It changes SONAME > libunbound.so.2 to libunbound.so.8. > > Dependent packages are: > asterisk > getdns > gnutls-dane > libreswan > netresolve-backends-ubdns > > I have prepared COPR repo with new build: > https://copr.fedorainfracloud.org/coprs/pemensik/unbound/packages/ > > asterisk package is failing on rawhide, because it uses /usr/bin/python > interpreter (bug #1633306). Other packages build fine with it. > > It is already pushed into rawhide but not yet built. I would like to > build new version on 8th October. > -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: 65C6C973 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Summary/Minutes from today's FESCo Meeting (2018-10-08)
= #fedora-meeting-1: FESCO (2018-10-08) = Meeting started by jforbes at 15:00:03 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-10-08/fesco.2018-10-08-15.00.log.html . Meeting summary --- * init process (jforbes, 15:00:03) * #1974 Problematic blocker for F29: dnf 'offline' module tracking (jforbes, 15:03:00) * LINK: https://pagure.io/fesco/issue/1974 (jforbes, 15:03:01) * AGREED: file fesco special final blocker on this, try and get more estimate input from dnf team (+7,0,-0) (jforbes, 15:18:50) * Next week's chair (jforbes, 15:19:05) * https://fedoraproject.org/wiki/Fedora_29_Beta_Release_Criteria#FESCo_blocker_bugs (zbyszek, 15:19:42) * ACTION: jforbes will file the blocker (jforbes, 15:20:05) * ACTION: contyk will chair next meeting (jforbes, 15:21:11) * Open Floor (jforbes, 15:21:27) Meeting ended at 15:26:01 UTC. Action Items * jforbes will file the blocker * contyk will chair next meeting Action Items, by person --- * contyk * contyk will chair next meeting * jforbes * jforbes will file the blocker * **UNASSIGNED** * (none) People Present (lines said) --- * jforbes (35) * bowlofeggs (26) * contyk (18) * nirik (12) * zodbot (12) * zbyszek (10) * sgallagh (9) * maxamillion (6) * tyll (0) * jsmith (0) Generated by `MeetBot`_ 0.1.4 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
Hi all, My thanks as well to Kamil for raising the question; it's been on my list of things to do for a while. The design of my patch set necessitates the allocation of one eventfd descriptor for each kernel handle (which is, sort of, the Windows equivalent of an fd) associated with a sync object. Some applications can use rather a lot of these; users have regularly run into the default limit of 4096. The 1M number comes from Debian and derivatives, which have this as their default hard limit (and is also the distribution I regularly use). I don't have any familiarity with the kernel or anything about the relevant infrastructure, but I don't see any reason why this would be unreasonable, and not just for my Wine patches specifically. On the other hand, I don't think it's quite necessary to go that high; many people have used a 200k limit, apparently successfully. (One badly misbehaving application, Google Earth VR, has a leak that causes it to allocate at least 300k descriptors, at least while loading, but I think that's the only one we've seen that has a leak on that scale. On the other hand 1M would be enough even for it.) One user reported 16k as being not enough for a more well-behaved game (I think it was Frostpunk); that's the highest lower bound I recall hearing. I've been meaning for a while to bring this up to the kernel itself; I certainly don't think 4096 seems like a reasonable limit these days, and that's not just as far as Wine and my patch set is concerned. ἔρρωσθε, Zeb ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
Allowing 1M open files per unprivileged process is too many. Megabytes of RAM are precious. A hard limit of 1M open files per process allows each process to eat at least 256MB (1M * sizeof(struct file) [linux/fs.h]) of RAM. If a single user is allowed 1000 processes, then that's 256GB of RAM, which is a Denial-of-Service attack. Yes, 4096 open files is not enough. Raise it to 65536. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
On 08/10/18 15:00, John Reiser wrote: > Allowing 1M open files per unprivileged process is too many. > > Megabytes of RAM are precious. A hard limit of 1M open files per process > allows each process to eat at least 256MB (1M * sizeof(struct file) > [linux/fs.h]) of RAM. If a single user is allowed 1000 processes, > then that's 256GB of RAM, which is a Denial-of-Service attack. > > Yes, 4096 open files is not enough. Raise it to 65536. > Correct me if I'm wrong, but wouldn't this be capped by the system-wide limit (i.e. it would hit ENFILE) before presenting a problem? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
On 10/8/18 2026 UTC, Zebediah Figura wrote: On 08/10/18 2000 UTC, John Reiser wrote: Allowing 1M open files per unprivileged process is too many. Megabytes of RAM are precious. A hard limit of 1M open files per process allows each process to eat at least 256MB (1M * sizeof(struct file) [linux/fs.h]) of RAM. If a single user is allowed 1000 processes, then that's 256GB of RAM, which is a Denial-of-Service attack. Yes, 4096 open files is not enough. Raise it to 65536. Correct me if I'm wrong, but wouldn't this be capped by the system-wide limit (i.e. it would hit ENFILE) before presenting a problem? That means that a different DoS can happen even sooner, at (ENFILE / 1M) processes. No other process could open() a file. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Fedocal] Reminder meeting : Modularity Office Hours
Dear all, You are kindly invited to the meeting: Modularity Office Hours on 2018-10-09 from 10:00:00 to 11:00:00 US/Eastern At fedora-modular...@chat.freenode.net The meeting will be about: This is where you ask the Fedora Modularity Team questions (and we try to answer them)! Join us on [IRC](irc://chat.freenode.net/#fedora-modularity): #fedora-modularity on [FreeNode](https://freenode.net) Source: https://apps.fedoraproject.org/calendar/meeting/5910/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Fedora 29 Branched 20181008.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 29 Branched 20181008.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: lorax - 20181005.n.0: lorax-29.12-2.fc29.src, 20181008.n.0: lorax-29.12-3.fc29.src anaconda - 20181005.n.0: anaconda-29.24.3-1.fc29.src, 20181008.n.0: anaconda-29.24.3-2.fc29.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/29 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20181008.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: raise fileno limit to make Steam Proton / Wine+esync work well in Fedora
On 08/10/18 16:43, John Reiser wrote: > On 10/8/18 2026 UTC, Zebediah Figura wrote: >> On 08/10/18 2000 UTC, John Reiser wrote: >>> Allowing 1M open files per unprivileged process is too many. >>> >>> Megabytes of RAM are precious. A hard limit of 1M open files per >>> process >>> allows each process to eat at least 256MB (1M * sizeof(struct file) >>> [linux/fs.h]) of RAM. If a single user is allowed 1000 processes, >>> then that's 256GB of RAM, which is a Denial-of-Service attack. >>> >>> Yes, 4096 open files is not enough. Raise it to 65536. >>> >> >> Correct me if I'm wrong, but wouldn't this be capped by the system-wide >> limit (i.e. it would hit ENFILE) before presenting a problem? > > That means that a different DoS can happen even sooner, > at (ENFILE / 1M) processes. No other process could open() a file. Sure, but in order to prevent that you'd almost always need to *lower* NOFILE. I don't know what kind of policies Fedora (or any other distribution) has regarding this kind of attack mitigation, but it seems dubious to me that this is worth doing. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 29 compose report: 20181008.n.0 changes
OLD: Fedora-29-20181005.n.0 NEW: Fedora-29-20181008.n.0 = SUMMARY = Added images:5 Dropped images: 18 Added packages: 6 Dropped packages:1 Upgraded packages: 250 Downgraded packages: 0 Size of added packages: 102.94 MiB Size of dropped packages:43.14 KiB Size of upgraded packages: 3.59 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -81.52 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Cloud_Base raw-xz s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-29-20181008.n.0.s390x.raw.xz Image: Everything boot armhfp Path: Everything/armhfp/iso/Fedora-Everything-netinst-armhfp-29-20181008.n.0.iso Image: Workstation boot armhfp Path: Workstation/armhfp/iso/Fedora-Workstation-netinst-armhfp-29-20181008.n.0.iso Image: Server boot armhfp Path: Server/armhfp/iso/Fedora-Server-netinst-armhfp-29-20181008.n.0.iso Image: Cloud_Base qcow2 s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-29-20181008.n.0.s390x.qcow2 = DROPPED IMAGES = Image: Xfce live i386 Path: Spins/i386/iso/Fedora-Xfce-Live-i386-29-20181005.n.0.iso Image: Security live x86_64 Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-29-20181005.n.0.iso Image: LXQt raw-xz armhfp Path: Spins/armhfp/images/Fedora-LXQt-armhfp-29-20181005.n.0-sda.raw.xz Image: Design_suite live i386 Path: Labs/i386/iso/Fedora-Design_suite-Live-i386-29-20181005.n.0.iso Image: Workstation raw-xz armhfp Path: Workstation/armhfp/images/Fedora-Workstation-armhfp-29-20181005.n.0-sda.raw.xz Image: Security live i386 Path: Labs/i386/iso/Fedora-Security-Live-i386-29-20181005.n.0.iso Image: Python_Classroom live x86_64 Path: Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-29-20181005.n.0.iso Image: Mate live i386 Path: Spins/i386/iso/Fedora-MATE_Compiz-Live-i386-29-20181005.n.0.iso Image: LXQt live x86_64 Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-29-20181005.n.0.iso Image: Design_suite live x86_64 Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-29-20181005.n.0.iso Image: Games live x86_64 Path: Labs/x86_64/iso/Fedora-Games-Live-x86_64-29-20181005.n.0.iso Image: Games live i386 Path: Labs/i386/iso/Fedora-Games-Live-i386-29-20181005.n.0.iso Image: Xfce live x86_64 Path: Spins/x86_64/iso/Fedora-Xfce-Live-x86_64-29-20181005.n.0.iso Image: Robotics live x86_64 Path: Labs/x86_64/iso/Fedora-Robotics-Live-x86_64-29-20181005.n.0.iso Image: LXQt live i386 Path: Spins/i386/iso/Fedora-LXQt-Live-i386-29-20181005.n.0.iso Image: Robotics live i386 Path: Labs/i386/iso/Fedora-Robotics-Live-i386-29-20181005.n.0.iso Image: Python_Classroom live i386 Path: Labs/i386/iso/Fedora-Python-Classroom-Live-i386-29-20181005.n.0.iso Image: Mate raw-xz armhfp Path: Spins/armhfp/images/Fedora-Mate-armhfp-29-20181005.n.0-sda.raw.xz = ADDED PACKAGES = Package: R-fs-1.2.6-1.fc29 Summary: Cross-Platform File System Operations Based on 'libuv' RPMs:R-fs Size:1.33 MiB Package: fedora-messaging-1.0.0-0.2.b1.fc29 Summary: Set of tools for using Fedora's messaging infrastructure RPMs:fedora-messaging fedora-messaging-doc python3-fedora-messaging Size:349.30 KiB Package: ghc-optparse-simple-0.1.0-1.fc29 Summary: Simple interface to optparse-applicative RPMs:ghc-optparse-simple ghc-optparse-simple-devel Size:712.06 KiB Package: openas2-2.6.2-2.fc29 Summary: Java-based implementation of the EDIINT AS2 standard RPMs:openas2 openas2-javadoc openas2-lib Size:1.82 MiB Package: racket-7.0-6.fc29 Summary: General purpose programming language RPMs:racket racket-collects racket-devel racket-doc racket-minimal racket-pkgs Size:97.42 MiB Package: s3fs-fuse-1.84-2.fc29 Summary: FUSE-based file system backed by Amazon S3 RPMs:s3fs-fuse Size:1.33 MiB = DROPPED PACKAGES = Package: python-workerpool-0.9.2-20.fc29 Summary: Multithreaded job distribution module RPMs:python2-workerpool python3-workerpool Size:43.14 KiB = UPGRADED PACKAGES = Package: CImg-1:2.3.6-1.fc29 Old package: CImg-202-5.fc29 Summary: C++ Template Image Processing Toolkit RPMs: CImg-devel Size: 10.84 MiB Size change: 2.97 MiB Changelog: * Wed Aug 01 2018 Daniel P. Berrang?? - 1:2.3.3-1 - Update to 2.3.3 release * Tue Sep 04 2018 Daniel P. Berrang?? - 1:2.3.6-1 - Update to 2.3.6 release Package: NetworkManager-openvpn-1:1.8.6-1.fc29 Old package: NetworkManager-openvpn-1:1.8.4-2.fc29 Summary: NetworkManager VPN plugin for OpenVPN RPMs: NetworkManager-openvpn NetworkManager-openvpn-gnome Size: 1.72 MiB Size change: -35.11 KiB Changelog: * Tue Oct 02 2018 Thomas Haller - 1:1.8.6-1 - Update to 1.8.6 release Package: OpenEXR-2.2.0-15.fc29 Old package: OpenEXR-2.2.0-14.fc29 Summary: A high dynamic-range (HDR) image file format RPMs: OpenEXR OpenEXR-devel OpenEXR-libs Size: 4.83 MiB Size change: -121.44 KiB Changelog: * Mon Oct 01 2018 Owen Taylor - 2.2.0-1
Fedora 29-20181008.n.0 compose check report
No missing expected images. Failed openQA tests: 10/133 (x86_64), 1/2 (arm) ID: 290770 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/290770 ID: 290779 Test: x86_64 Workstation-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/290779 ID: 290790 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/290790 ID: 290807 Test: x86_64 KDE-live-iso base_services_start URL: https://openqa.fedoraproject.org/tests/290807 ID: 290808 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/290808 ID: 290809 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/290809 ID: 290812 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/290812 ID: 290817 Test: x86_64 universal install_blivet_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/290817 ID: 290841 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/290841 ID: 290847 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/290847 ID: 290888 Test: x86_64 universal install_rescue_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/290888 Soft failed openQA tests: 9/133 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 290751 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/290751 ID: 290752 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/290752 ID: 290754 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/290754 ID: 290774 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/290774 ID: 290775 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/290775 ID: 290798 Test: x86_64 KDE-live-iso install_no_user URL: https://openqa.fedoraproject.org/tests/290798 ID: 290820 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/290820 ID: 290830 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/290830 ID: 290858 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/290858 ID: 290868 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/290868 ID: 290883 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/290883 Passed openQA tests: 114/133 (x86_64), 22/24 (i386) Skipped openQA tests: 1 of 159 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Test-Announce] Fedora 29 Final Freeze
Hi all, Today, October 09th 2018, is an important day on the Fedora 29 schedule [1], with significant cut-offs. Today we have the Final Freeze [2]. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedoraproject.org/wiki/Releases/29/Schedule [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/29/final/buglist Regards, Release Engineering ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
