[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20240409134311.11505-1-aha310510@gmail.com>
Date: Tue,  9 Apr 2024 22:43:11 +0900
From: Jeongjun Park <aha310510@...il.com>
To: kuniyu@...zon.com
Cc: aha310510@...il.com,
	daan.j.demeyer@...il.com,
	davem@...emloft.net,
	dsahern@...nel.org,
	edumazet@...gle.com,
	eric.dumazet@...il.com,
	kuba@...nel.org,
	martin.lau@...nel.org,
	netdev@...r.kernel.org,
	pabeni@...hat.com,
	willemdebruijn.kernel@...il.com
Subject: Re: [PATCH net] net: implement lockless setsockopt(SO_PEEK_OFF)
Kuniyuki Iwashima wrote:
> It might mitigate your risk, but it does not exist upstream.
> We don't accept such a patch that adds unnecessary locks just
> for a future possible issue.  It should be fixed when such an
> option requiring u->iolock is added.
Ah i see.
I learned that you should not carelessly patch major code 
considering potential elements that do not immediately exist upstream.
Thanks.
Powered by blists - more mailing lists
 
