On Mon, Apr 27, 2026 at 09:33:12AM -0600, Greg KH wrote: > On Mon, Apr 27, 2026 at 05:24:06PM +0200, Willy Tarreau wrote: > > On Mon, Apr 27, 2026 at 07:49:08AM -0600, Greg KH wrote: > > > On Sun, Apr 26, 2026 at 06:39:12PM +0200, Willy Tarreau wrote: > > > > With the increase of automated reports, the security team is dealing > > > > with way more messages than really needed. The reporting process works > > > > well with most teams so there is no need to systematically involve the > > > > security team in reports. > > > > > > > > Let's suggest to keep it for small lists of recipients, to cover the > > > > risk of lost messages (spam, vacation etc) but to avoid it for larger > > > > teams. > > > > > > > > Cc: Greg KH <[email protected]> > > > > Cc: Leon Romanovsky <[email protected]> > > > > Signed-off-by: Willy Tarreau <[email protected]> > > > > > > This is going to cut down on emails to us a bunch, which might be good, > > > or not, as now we'll not have a way to know what's going on overall. > > > But hey, let's try it and see what happens! > > > > Or maybe we could suggest that first reports from a reporter should > > always Cc the list ? After all, every time we asked to drop the list > > was for senders at their 5th or 10th submission. Maybe we could just > > say that the list members prefer not being repetitively CCed by the > > same submitters to invest more time on newcomers ? > > Yes, that might be better, otherwise maintainers are going to get some > pretty foolish reports with out the context of howing to properly at > least push back on them, like we have gotten good at doing :)
Yes, and more importantly, we know how to react while some maintainers getting their first report are stressed. Let me try to rework it. Thanks! Willy
