Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+0\/2\]\s+Drop\s+IPVS\s+conn\s+templates\s+under\s+attack\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+0\/2\]\s+Drop\s+IPVS\s+conn\s+templates\s+under\s+attack\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH net-next 0/2] Drop IPVS conn templates under attack (score: 1): Author: Michal Koutnı <mkoutny@xxxxxxxx>; Date: Tue, 5 Jun 2018 17:43:37 +0200; Thanks for looking into this and generalizing it. I just want to confirm your patchset also yields the desired behavior wrt non-accumulation of the template entries in my tests. Michal Attachment: si; /html/lvs-devel/2018-06/msg00015.html (10,769 bytes)
2. [PATCH net-next 0/2] Drop IPVS conn templates under attack (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sat, 2 Jun 2018 21:50:00 +0300; This patchset implements assured flag for connection templates in first patch, so that the second patch can use it to decide if to drop connection templates under attack. The patchset is based on imp; /html/lvs-devel/2018-06/msg00004.html (10,164 bytes)

Current List: 1 - 2
Page: [1]