All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <fw@strlen.de>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<kuni1840@gmail.com>, <kuniyu@amazon.com>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>,
	<syzbot+444ca0907e96f7c5e48b@syzkaller.appspotmail.com>
Subject: Re: [PATCH v1 net] udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
Date: Thu, 25 May 2023 10:06:53 -0700	[thread overview]
Message-ID: <20230525170653.99846-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20230525163342.GB25057@breakpoint.cc>

From: Florian Westphal <fw@strlen.de>
Date: Thu, 25 May 2023 18:33:42 +0200
> Kuniyuki Iwashima <kuniyu@amazon.com> wrote:
> > > I'd remove it in -next.  Same for DCCP.
> > 
> > Ok, I'll do for UDP Lite.
> 
> Thanks.
> 
> > +1 for DCCP, but we know there are real?
> > still experimenting? users ... ?
> 
> Yes, and they can continue to work on their out of tree fork
> and research projects, no problem.
> 
> I'd say next time some net/core change needs dccp changes,
> remove dccp first (or mark it as CONFIG_BROKEN) so it doesn't
> cause extra work.

FWIW, I was going to post such a patch that removes .twsk_unique
and .twsk_destructor handler in timewait_sock_ops, which is only
used by TCP but exists just because DCCP shares the struct.


> DCCP can be brought back when someone has interest to maintain it.
> 
> Looking at DCCP patches its either:
> 1. odd syzbot fixes
> 2. api changes in net that need folloup changes in dccp
> 3. automated transformations
> 
> There is no sign that anyone is maintaining this (or running it
> in a production environment...).

Exactly.  It's now kind of bleeding ground of CVE.

Actualy, we disable CONFIG_IP_DCCP for our latest distribution (AL2023)
for the reason, and RHEL 7.8+ also prevents the module from being loaded
by default.

If there's no objection, I can remove it after UDP Lite.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.8_release_notes/deprecated_functionality#automatic_loading_of_dccp_modules_through_socket_layer_is_now_disabled_by_default

  reply	other threads:[~2023-05-25 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 16:33 [PATCH v1 net] udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated() Kuniyuki Iwashima
2023-05-25  8:59 ` Paolo Abeni
2023-05-25 15:10   ` Kuniyuki Iwashima
2023-05-25 15:18     ` Florian Westphal
2023-05-25 16:21       ` Kuniyuki Iwashima
2023-05-25 16:33         ` Florian Westphal
2023-05-25 17:06           ` Kuniyuki Iwashima [this message]
2023-05-25  9:20 ` patchwork-bot+netdevbpf

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=20230525170653.99846-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+444ca0907e96f7c5e48b@syzkaller.appspotmail.com \
    /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.