public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuni1840@gmail.com>
To: hch@lst.de
Cc: axboe@kernel.dk, chuck.lever@oracle.com, davem@davemloft.net,
	edumazet@google.com, horms@kernel.org, jaka@linux.ibm.com,
	jlayton@kernel.org, kbusch@kernel.org, kuba@kernel.org,
	kuni1840@gmail.com, kuniyu@amazon.com, linux-nfs@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org,
	matttbe@kernel.org, mptcp@lists.linux.dev,
	netdev@vger.kernel.org, pabeni@redhat.com, sfrench@samba.org,
	wenjia@linux.ibm.com, willemb@google.com
Subject: Re: [PATCH v2 net-next 1/7] socket: Un-export __sock_create().
Date: Thu, 29 May 2025 19:42:36 -0700	[thread overview]
Message-ID: <20250530024238.3205130-1-kuni1840@gmail.com> (raw)
In-Reply-To: <20250526052907.GB11639@lst.de>

From: Christoph Hellwig <hch@lst.de>
Date: Mon, 26 May 2025 07:29:07 +0200
> On Fri, May 23, 2025 at 11:21:07AM -0700, Kuniyuki Iwashima wrote:
> > Since commit eeb1bd5c40ed ("net: Add a struct net parameter to
> > sock_create_kern"), we no longer need to export __sock_create()
> > and can replace all non-core users with sock_create_kern().
> > 
> > Let's convert them and un-export __sock_create().
> 
> The changes looks good, but the commit log including subject line
> is rather confusing.  What you do is to replace all uses of
> __sock_create with sock_create_kern, which works because
> sock_create_kern just calls __sock_create with the last argument set
> to 1 as those callers do it.  This then allows marking __sock_create
> static because all outside users are gone.
> 
> Please state that, i.e.

Will do so.

Thanks!

> 
> Subect: use sock_create_kern insteadf of opencoding it
> 
> Replace all callers of __sock_create that set the kernel argument to 1
> with sock_create_kern, which is the improve interface for that.
> Mark __sock_create static now that all users outside of socket.c
> are gone.

  parent reply	other threads:[~2025-05-30  2:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 18:21 [PATCH v2 net-next 0/7] socket: Make sock_create_kern() robust against misuse Kuniyuki Iwashima
2025-05-23 18:21 ` [PATCH v2 net-next 1/7] socket: Un-export __sock_create() Kuniyuki Iwashima
2025-05-26  5:29   ` Christoph Hellwig
2025-05-26 10:06     ` David Laight
2025-05-30  2:42     ` Kuniyuki Iwashima [this message]
2025-05-23 18:21 ` [PATCH v2 net-next 2/7] socket: Rename sock_create_kern() to __sock_create_kern() Kuniyuki Iwashima
2025-05-26  5:30   ` Christoph Hellwig
2025-05-29 21:29     ` David Laight
2025-05-30  3:05       ` Kuniyuki Iwashima
2025-05-30  6:48         ` David Laight
2025-05-30  2:45     ` Kuniyuki Iwashima
2025-05-23 18:21 ` [PATCH v2 net-next 3/7] socket: Restore sock_create_kern() Kuniyuki Iwashima
2025-05-26  5:32   ` Christoph Hellwig
2025-05-30  2:53     ` Kuniyuki Iwashima
2025-06-02  5:08       ` Christoph Hellwig
2025-06-03 21:30         ` David Laight
2025-06-04 18:36           ` Kuniyuki Iwashima
2025-05-23 18:21 ` [PATCH v2 net-next 4/7] smb: client: Add missing net_passive_dec() Kuniyuki Iwashima
2025-05-23 18:21 ` [PATCH v2 net-next 5/7] socket: Remove kernel socket conversion except for net/rds/ Kuniyuki Iwashima
2025-05-26  5:33   ` Christoph Hellwig
2025-05-30  2:59     ` Kuniyuki Iwashima
2025-06-02  5:08       ` Christoph Hellwig
2025-05-23 18:21 ` [PATCH v2 net-next 6/7] socket: Replace most sock_create() calls with sock_create_kern() Kuniyuki Iwashima
2025-05-26  5:33   ` Christoph Hellwig
2025-05-26  5:35   ` Christoph Hellwig
2025-05-30  3:03     ` Kuniyuki Iwashima
2025-06-02  5:09       ` Christoph Hellwig
2025-06-02 21:52         ` Kuniyuki Iwashima
2025-06-03  4:50           ` Christoph Hellwig
2025-06-04 18:20             ` Kuniyuki Iwashima
2025-06-05  4:28               ` Christoph Hellwig
2025-05-23 18:21 ` [PATCH v2 net-next 7/7] socket: Clean up kdoc for sock_create() and sock_create_lite() Kuniyuki Iwashima

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=20250530024238.3205130-1-kuni1840@gmail.com \
    --to=kuni1840@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hch@lst.de \
    --cc=horms@kernel.org \
    --cc=jaka@linux.ibm.com \
    --cc=jlayton@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sfrench@samba.org \
    --cc=wenjia@linux.ibm.com \
    --cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox