[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240416214750.29461-1-kuniyu@amazon.com>
Date: Tue, 16 Apr 2024 14:47:50 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <rao.shoaib@...cle.com>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<kuni1840@...il.com>, <kuniyu@...zon.com>, <netdev@...r.kernel.org>,
<pabeni@...hat.com>
Subject: Re: [PATCH v2 net 2/2] af_unix: Don't peek OOB data without MSG_OOB.
From: Rao Shoaib <rao.shoaib@...cle.com>
Date: Tue, 16 Apr 2024 14:34:20 -0700
> On 4/16/24 13:51, Kuniyuki Iwashima wrote:
> > From: Rao Shoaib <rao.shoaib@...cle.com>
> > Date: Tue, 16 Apr 2024 13:11:09 -0700
> >> The proposed fix is not the correct fix as among other things it does
> >> not allow going pass the OOB if data is present. TCP allows that.
> >
> > Ugh, exactly.
> >
> > But the behaviour was broken initially, so the tag is
> >
> > Fixes: 314001f0bf92 ("af_unix: Add OOB support")
> >
>
> Where is this requirement listed?
Please start with these docs.
https://docs.kernel.org/process/submitting-patches.html
https://docs.kernel.org/process/maintainer-netdev.html
>
>
> > Could you post patches formally on top of the latest net.git ?
> > It seems one of my patch is squashed.
>
> I pulled in last night, your last fix has not yet made it (I think)
>
> [rshoaib@...bo-2 linux_oob]$ git describe
> v6.9-rc4-32-gbf541423b785
Probably you are using another git tree or branch.
Networking subsystem uses net.git for fixes and net-next.git for new
features as written in the 2nd doc above.
My patch landed on 4 days ago at least.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=283454c8a123072e5c386a5a2b5fc576aa455b6f
Also you should receive this email.
https://lore.kernel.org/netdev/171297422982.31124.3409808601326947596.git-patchwork-notify@kernel.org/
>
> >
> > Also, please note that one patch should fix one issue.
> > The change in queue_oob() should be another patch.
> >
>
> I was just responding to your email. I was not sure if you wanted to
> modify your fix. If you prefer I submit the patches, I will later.
As I said, my fix is already in net.git, so you can post a separte
patch based on net.git/main.
Powered by blists - more mailing lists