Documentation/networking/ip-sysctl.txt:46 says:
ip_forward_use_pmtu - BOOLEAN
By default we don't trust protocol path MTUs while forwarding
because they could be easily forged and can lead to unwanted
fragmentation by the router.
You only need to enable this if you have user-space software
which tries to discover path mtus by itself and depends on the
kernel honoring this information. This is normally not the case.
Default: 0 (disabled)
Possible values:
0 - disabled
1 - enabled
Which makes it pretty clear that setting it to 1 is a potential
security/safety/DoS issue, and yet it is entirely reasonable to want
forwarded traffic to honour explicitly administrator configured
route mtus (instead of defaulting to device mtu).
Indeed, I can't think of a single reason why you wouldn't want to.
Since you configured a route mtu you probably know better...
It is pretty common to have a higher device mtu to allow receiving
large (jumbo) frames, while having some routes via that interface
(potentially including the default route to the internet) specify
a lower mtu.
Note that ipv6 forwarding uses device mtu unless the route is locked
(in which case it will use the route mtu).
This approach is not usable for IPv4 where an 'mtu lock' on a route
also has the side effect of disabling TCP path mtu discovery via
disabling the IPv4 DF (don't frag) bit on all outgoing frames.
I'm not aware of a way to lock a route from an IPv6 RA, so that also
potentially seems wrong.
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Willem de Bruijn <willemb@google.com>
Cc: Lorenzo Colitti <lorenzo@google.com>
Cc: Sunmeet Gill (Sunny) <sgill@qti.qualcomm.com>
Cc: Vinay Paradkar <vparadka@qti.qualcomm.com>
Cc: Tyler Wear <twear@qti.qualcomm.com>
Cc: David Ahern <dsahern@kernel.org>
Reviewed-by: Eric Dumazet <edumazet@google.com>
(Backported from commit 02a1b175b0e92d9e0fa5df3957ade8d733ceb6a0).
Change-Id: I26f336f891711f0149b2835d2c4a78fc8407b5ba
Git-Commit: 02a1b175b0e92d9e0fa5df3957ade8d733ceb6a0
Git-repo: https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux
Signed-off-by: Sauvik Saha <ssaha@codeaurora.org>
Structure pointer added in list was not deleted properly.
Delete list in proper sequence and free pointer.
Change-Id: I9a5deb0801ec7366d0be7049e8771016a3bbdf44
Signed-off-by: Naman Padhiar <npadhiar@codeaurora.org>
Send MSA segment of DDR to FW with IOVA range as part of
Host Capability. So that FW detect invalid host DDR access
before SMMU fault happens.
Change-Id: I21c011b50c54f37dd7b5a942e1914c1afdf6d766
Signed-off-by: Naman Padhiar <npadhiar@codeaurora.org>
Enables ufs debug feature for general/debug builds.
Disables this feature for perf builds.
Change-Id: I2b30c8081d24db7871c277c67631d92fc7d9ea60
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
This sysfs entry provides the state of the driver.
If it's in debug/perf state.
This can be used by user-space scripts to toggle various tracing.
Change-Id: If0e3d8e032f60c9134bdd5ce27fe37687e67770a
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
Enable IPC logging for functionalities like diag, adb
and mtp that uses the f_fs driver on Holi.
Change-Id: I9f627f74d3b34b69da6da8d3390dc5f3eee95f14
Signed-off-by: Sriharsha Allenki <sallenki@codeaurora.org>
Currently GSI endpoint usb_request pointer is allocated only once
during boot time and it used by dwc3 driver for mapping doorbell register
address with USB endpoint request only once. During composition switch
or connect/disconnect scenarios same USB endpoint is being re-enabled and
does not create mapping again.
On some platforms multiple UDC cores can work in device mode. In case
of binding the UDC with primary controller first and then disconnect the
primary and bind UDC to secondary controller. Driver does not re-mapping
the doorbell address with current UDC core and USB GSI wrapper is trying
to access previously mapped GSI DBL address with previous core
resulting into smmu fault.
Fix this issue by adding re-mapping of doorbell using dwc->sysdev node
to map the doorbell register with correct UDC.
Change-Id: I327126148c2311884aee2aa99bb59b7add06e302
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
This module is used to tunnel multicast
packets received on an interface to WLAN
clients which have registered for these
packet streams. Mainly used to tunnel
EMBMS packets received on TMGI streams.
Change-Id: I996077342261ec2cb688e98319c6881d2dd7cce2
Acked-by: Raju Velpula <rvelpula@qti.qualcomm.com>
Signed-off-by: Paras Singh Jain <parassin@codeaurora.org>
