You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
suricata/doc
Victor Julien 37a871d96f nfs: bound partial metadata replies with max-metadata-size
A partial v3 reply that carries no file data is skipped rather than
buffered toward its claim, which for LOOKUP, READDIRPLUS and CREATE drops
the handle to name mapping their replies establish. The exception to that
reused max-read-size, so those procedures depended on a knob that
documents READ data, and lowering it for READs silently dropped the
mapping of any directory reply above it; the mapping depends on
segmentation, as the same reply parses when it arrives in one piece.

Give them a limit of their own, max-metadata-size, with a 16 MiB default,
and use it to decide whether such a reply may still buffer toward its
record claim. A value of 0 falls back to the default, so the buffering
stays bounded and the limit cannot be disabled. The WRITE and READ limits
share that default through NFS_MAX_RW_SIZE_DEFAULT. Documented in the
userguide.

Ticket: #9263.
19 hours ago
..
doxygen
…
userguide nfs: bound partial metadata replies with max-metadata-size 19 hours ago
AUTHORS
…
Basic_Setup.txt docs: fix typos in Basic_Setup.txt 4 months ago
INSTALL
…
Makefile.am
…
NEWS
…
README
…
Setting_up_IPSinline_for_Linux.txt
…
TODO
…
Third_Party_Installation_Guides.txt
…

README