In the quest to remove all stack VLAs from the kernel[1], this refactors
the stack array size calculation to avoid using max(), which makes the
compiler think the size isn't fixed.
[1] https://lkml.org/lkml/2018/3/7/621
Signed-off-by: Kees Cook
---
net/ipv4/proc.c | 10 --
net/ipv6/proc
From: Roopa Prabhu
add support to match on ip_proto, sport and dport ranges.
For ip_proto, this patch currently enumerates, tcp, udp and sctp.
This list can be extended in the future.
example:
$ip rule add sport 666-777 dport 999 ip_proto tcp table 100
$ip rule show
0: from all lookup local
From: Deepa Dinamani
[ Upstream commit d340266e19ddb70dbd608f9deedcfb35fdb9d419 ]
struct timespec is not y2038 safe on 32 bit machines.
The posix clocks apis use struct timespec directly and through struct
itimerspec.
Replace the posix clock interfaces to use struct timespec64 and struct
itime
From: Intiyaz Basha
Corrected length check when data received in the mbox is more than one
64 bit data value
Signed-off-by: Intiyaz Basha
Signed-off-by: Felix Manlunas
---
drivers/net/ethernet/cavium/liquidio/octeon_mailbox.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --
From: Prasad Kanneganti
Avoid doing useless work by making sure that the response_list is not empty
before scheduling work to process it.
Signed-off-by: Prasad Kanneganti
Signed-off-by: Felix Manlunas
---
drivers/net/ethernet/cavium/liquidio/request_manager.c | 5 +
drivers/net/ethernet/
From: Deepa Dinamani
[ Upstream commit d340266e19ddb70dbd608f9deedcfb35fdb9d419 ]
struct timespec is not y2038 safe on 32 bit machines.
The posix clocks apis use struct timespec directly and through struct
itimerspec.
Replace the posix clock interfaces to use struct timespec64 and struct
itime
Sorry, this is way too large of a patch series.
Please keep your series to about a dozen or so changes.
Anything longer puts an unreasonable burdon upon patch
reviewers, and such a large series will often make it
so that nearly all reviewers are discouraged from taking
a look at all.
Thank you.
Hi,
I don't see fe9c842695e2 ("NFC: llcp: Limit size of SDP URI") queued
up for stable. Can this one be added please? This is a buffer overflow
fix.
Thanks!
-Kees
--
Kees Cook
Pixel Security
From: Veerasenareddy Burru
In a scenario where the command queued to firmware get dropped or times
out, MTU change from host will not propagate to firmware. So, it is
required for host driver to wait for response from firmware or timeout
and then return correct status to caller of ndo_change_mtu.
301 - 309 of 309 matches
Mail list logo