From owner-freebsd-bugs@freebsd.org Mon Aug 19 23:33:09 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F00ADD5091 for ; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46C9GF65bDz4ZQn for ; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CF86FD5090; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CF4E9D508F for ; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46C9GF58rrz4ZQl for ; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9309922372 for ; Mon, 19 Aug 2019 23:33:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7JNX9SJ034784 for ; Mon, 19 Aug 2019 23:33:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7JNX9uN034783 for bugs@FreeBSD.org; Mon, 19 Aug 2019 23:33:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239980] Allowing maximum value to option "-l" in combination with option "-G", "-g", "-s" and "-f" makes system (host and guest) in freeze/hang condition by eating full CPU and RAM resources Date: Mon, 19 Aug 2019 23:33:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: neerajpal09@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2019 23:33:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239980 Bug ID: 239980 Summary: Allowing maximum value to option "-l" in combination with option "-G", "-g", "-s" and "-f" makes system (host and guest) in freeze/hang condition by eating full CPU and RAM resources Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: neerajpal09@gmail.com There is a issue after running the command given below on my FreeBSD virtual machine, it suddenly start eating my all CPU and RAM resources and I have observed the hangs/freezing behaviour on my guest machine which also impacts the host machine in 10-30 seconds. After observing such behaviour I am sure that after leaving it for some min= utes or hours. It could lead to DOS. * ping -s 56 -G 4294967297 -g 4294967292 -l 429496729 -f localhost or * ping -s 56 -G maximum_allowed_value -g minimum_allowed_value -l 429496729= -f localhost I think it should not allowed to preload (-l) this much value, especially w= ith option "-f". top(1) info given below (only in 13 seconds this much usage): PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMM= AND 2456 root 1 93 0 11M 2604K CPU2 2 0:13 99.51% ping 723 root 1 94 0 21M 9848K CPU3 3 1:21 91.98% sshd I am connected via ssh and have observed that everytime when I run the above mentioned ping command then the usage of sshd daemon also increases suddenly (as given in the above top(1) info). --=20 You are receiving this mail because: You are the assignee for the bug.=