netdev - RE: [PATCH 1/1] net: sctp: dynamically enable or disable pf state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 14 Dec 2015 09:53:58 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	"'zyjzyj2000@...il.com'" <zyjzyj2000@...il.com>,
	"vyasevich@...il.com" <vyasevich@...il.com>,
	"nhorman@...driver.com" <nhorman@...driver.com>,
	"linux-sctp@...r.kernel.org" <linux-sctp@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"alexandre.dietsch@...driver.com" <alexandre.dietsch@...driver.com>,
	"stefan.costandache@...driver.com" <stefan.costandache@...driver.com>
Subject: RE: [PATCH 1/1] net: sctp: dynamically enable or disable pf state

From: zyjzyj2000@...il.com
> Sent: 11 December 2015 09:06
...
> +pf_enable - INTEGER
> +	Enable or disable pf state. A value of pf_retrans > path_max_retrans
> +	also disables pf state. That is, one of both pf_enable and
> +	pf_retrans > path_max_retrans can disable pf state. Since pf_retrans
> +	and path_max_retrans can be changed by userspace application, sometimes
> +	user expects to disable pf state by the value of
> +	pf_retrans > path_max_retrans, but ocassionally the value of pf_retrans
> +	or path_max_retrans is changed by the user application, this pf state is
> +	enabled. As such, it is necessary to add this to dynamically enable
> +	and disable pf state.
> +
> +	1: Enable pf.
> +
> +	0: Disable pf.
> +
> +	Default: 1

You ought to say what 'pf' is short for.

	David

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html