All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Sven Eckelmann <sven@narfation.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Simon Horman <horms@kernel.org>,
	b.a.t.m.a.n@lists.open-mesh.org,
	Simon Wunderlich <sw@simonwunderlich.de>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28
Date: Tue, 4 Aug 2026 15:14:27 -0700	[thread overview]
Message-ID: <20260804151427.48602ee8@kernel.org> (raw)
In-Reply-To: <dbd0dc17-d097-4254-b6f0-59eeb6e69579@redhat.com>

On Tue, 4 Aug 2026 20:32:21 +0200 Paolo Abeni wrote:
> > Sorry, I am lost. There is stuff for which people have actual PoC code. Afaik, 
> > nothing for an RCE but enough to locally be a minor annoyance. The things 
> > which have no "Reported-by" are things which I have problems with on my 
> > installations.
> > 
> > And about the others: The "bla: avoid CRC corruption due to parallel claim 
> > add" + "prevent CRC corruptions after claim flush" were a problems I had (next 
> > to another which was not yet posted to netdev) but has a "Reported-by: 
> > Sashiko" because it was also reported by Sashiko when posting other bla 
> > patches and I think I've stolen the example from the commit message partially 
> > from the Sashiko report.  
> 
> I'm sorry this is getting more complicated than really intended. The
> rule of thumb is that real problems actually bothering users go into the
> 'net' tree, and other stuff goes into net-next without the fixes tag.

My rule of thumb is "there is no such thing as 'worth backporting but
not worth net'". People tend to send to -next fixes they didn't bother
testing.

      reply	other threads:[~2026-08-04 22:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 13:39 [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28 Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 01/15] batman-adv: bla: avoid CRC corruption due to parallel claim add Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 02/15] batman-adv: bla: prevent CRC corruptions after claim flush Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 03/15] batman-adv: dat: avoid unaligned fault in IP extraction Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 04/15] batman-adv: dat: atomically update mac addresses Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 05/15] batman-adv: fix TX priority extraction for BATADV_FORW_MCAST Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 06/15] batman-adv: mcast: ensure unshared skb for multicast packets Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 07/15] batman-adv: mcast: linearize skbuff for packet generation Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 08/15] batman-adv: dat: drop non-4addr backwards compatibility Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 09/15] batman-adv: add missing kernel-doc comments Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 10/15] batman-adv: fix kernel-doc for functions holding skb ownership Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 11/15] batman-adv: annotate functions which may reallocate the skbuff Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 12/15] batman-adv: split multiple declarations per line Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 13/15] batman-adv: switch var declarations to reverse x-mas tree order Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 14/15] batman-adv: tt: use atomic flag modifications Simon Wunderlich
2026-07-28 13:39 ` [PATCH net-next 15/15] batman-adv: tt: simplify NEW flag transition code Simon Wunderlich
2026-08-04  2:19 ` [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28 Jakub Kicinski
2026-08-04  6:55   ` Sven Eckelmann
2026-08-04 13:16     ` Paolo Abeni
2026-08-06 14:49       ` Sven Eckelmann
2026-08-04 10:19 ` Paolo Abeni
2026-08-04 10:38   ` Sven Eckelmann
2026-08-04 13:08     ` Paolo Abeni
2026-08-04 15:05       ` Sven Eckelmann
2026-08-04 18:32         ` Paolo Abeni
2026-08-04 18:32           ` Paolo Abeni
2026-08-04 22:14           ` Jakub Kicinski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260804151427.48602ee8@kernel.org \
    --to=kuba@kernel.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.