/// Bool initializations should use true and false. Bool tests don't need /// comparisons. Based on contributions from Joe Perches, Rusty Russell /// and Bruce W Allan. /// // Confidence: High // Copyright: (C) 2012 Julia Lawall, INRIA/LIP6. GPLv2. // Copyright: (C) 2012 Gilles Muller, INRIA/LiP6. GPLv2. // URL: http://coccinelle.lip6.fr/ // Options: --include-headers virtual patch virtual context virtual org virtual report @depends on patch@ bool t; symbol true; symbol false; @@ ( - t == true + t | - true == t + t | - t != true + !t | - true != t + !t | - t == false + !t | - false == t + !t | - t != false + t | - false != t + t ) @depends on patch disable is_zero, isnt_zero@ bool t; @@ ( - t == 1 + t | - t != 1 + !t | - t == 0 + !t | - t != 0 + t ) @depends on patch@ bool b; @@ ( b = - 0 + false | b = - 1 + true ) // --------------------------------------------------------------------- @r1 depends on !patch@ bool t; position p; @@ ( * t@p == true | * true == t@p | * t@p != true | * true != t@p | * t@p == false | * false == t@p | * t@p != false | * false != t@p ) @r2 depends on !patch disable is_zero, isnt_zero@ bool t; position p; @@ ( * t@p == 1 | * t@p != 1 | * t@p == 0 | * t@p != 0 ) @r3 depends on !patch@ bool b; position p1,p2; constant c; @@ ( *b@p1 = 0 | *b@p1 = 1 | *b@p2 = c ) @script:python depends on org@ p << r1.p; @@ cocci.print_main("WARNING: Comparison to bool",p) @script:python depends on org@ p << r2.p; @@ cocci.print_main("WARNING: Comparison of bool to 0/1",p) @script:python depends on org@ p1 << r3.p1; @@ cocci.print_main("WARNING: Assignment of bool to 0/1",p1) @script:python depends on org@ p2 << r3.p2; @@ cocci.print_main("ERROR: Assignment of bool to non-0/1 constant",p2) @script:python depends on report@ p << r1.p; @@ coccilib.report.print_report(p[0],"WARNING: Comparison to bool") @script:python depends on report@ p << r2.p; @@ coccilib.report.print_report(p[0],"WARNING: Comparison of bool to 0/1") @script:python depends on report@ p1 << r3.p1; @@ coccilib.report.print_report(p1[0],"WARNING: Assignment of bool to 0/1") @script:python depends on report@ p2 << r3.p2; @@ coccilib.report.print_report(p2[0],"ERROR: Assignment of bool to non-0/1 constant") git.cgi/linux/net-next.git/log/include/crypto/internal/scompress.h'>
path: root/include/crypto/internal/scompress.h
diff options
context:
space:
mode:
authorKalle Valo <kvalo@codeaurora.org>2017-01-27 14:19:25 +0200
committerKalle Valo <kvalo@codeaurora.org>2017-01-28 09:15:50 +0200
commit2b1d530cb3157f828fcaadd259613f59db3c6d1c (patch)
treefb5dfe8f2e6956f54377c7275f330cd158ead259 /include/crypto/internal/scompress.h
parentbd19b5ab1da654de456e102250822ec06311d6ad (diff)
MAINTAINERS: ath9k-devel is closed
ath9k-devel list is now closed, only linux-wireless should be used. Reported-by: Michael Renzmann <mrenzmann@madwifi-project.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'include/crypto/internal/scompress.h')
s once in the kernel. This patch series addresses both of these issues. The queues are fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/mac80211/debugfs_sta.c')