public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17252] getrandom and getentropy syscall Date: Tue, 24 Feb 2015 14:34:00 -0000 [thread overview] Message-ID: <bug-17252-131-LqIXeSVuOk@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17252-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17252 --- Comment #4 from Cristian Rodríguez <crrodriguez at opensuse dot org> --- (In reply to Victor Stinner from comment #3) > Any progress on this issue? I would be interested to use it in Python to > avoid issues with the /dev/urandom file descriptor: > http://bugs.python.org/issue22181 use the syscall() interface for now. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-27610-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Feb 24 15:38:34 2015 Return-Path: <glibc-bugs-return-27610-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 95606 invoked by alias); 24 Feb 2015 15:38:34 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 95562 invoked by uid 48); 24 Feb 2015 15:38:30 -0000 From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/14889] svc_run() produces high cpu usage when accept() fails with EMFILE (CVE-2011-4609) Date: Tue, 24 Feb 2015 15:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: network X-Bugzilla-Version: 2.17 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security+ X-Bugzilla-Changed-Fields: short_desc alias Message-ID: <bug-14889-131-Rlu5c5GpN9@http.sourceware.org/bugzilla/> In-Reply-To: <bug-14889-131@http.sourceware.org/bugzilla/> References: <bug-14889-131@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-02/txt/msg00345.txt.bz2 Content-length: 661 https://sourceware.org/bugzilla/show_bug.cgi?id\x14889 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|CVE-2011-4609 svc_run() |svc_run() produces high cpu |produces high cpu usage |usage when accept() fails |when accept() fails with |with EMFILE (CVE-2011-4609) |EMFILE | Alias| |CVE-2011-4609 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-02-24 14:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-10 17:04 [Bug libc/17252] New: " crrodriguez at opensuse dot org 2014-08-11 15:47 ` [Bug libc/17252] " joseph at codesourcery dot com 2014-08-11 20:49 ` fweimer at redhat dot com 2014-08-16 16:54 ` fweimer at redhat dot com 2014-10-06 13:38 ` alex.gaynor at gmail dot com 2015-02-24 14:21 ` victor.stinner at gmail dot com 2015-02-24 14:34 ` crrodriguez at opensuse dot org [this message] 2015-08-14 14:17 ` nmav at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17252-131-LqIXeSVuOk@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).