lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZafBxnhOSWxBRWko@debian>
Date: Wed, 17 Jan 2024 13:02:13 +0100
From: Alejandro Colomar <alx@...nel.org>
To: Petr Vorel <pvorel@...e.cz>
Cc: linux-man@...r.kernel.org,
	Maciej Żenczykowski <maze@...gle.com>,
	linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
	Matthias Gerstner <matthias.gerstner@...e.com>,
	Avinesh Kumar <akumar@...e.de>
Subject: Re: [PATCH 1/1] socket.7: Mention CAP_NET_RAW on SO_MARK

Hi Petr,

On Wed, Jan 17, 2024 at 10:14:52AM +0100, Petr Vorel wrote:
> Hi Alex,
> 
> > Hi Petr,
> 
> > On Tue, Jan 16, 2024 at 12:04:18PM +0100, Petr Vorel wrote:
> > > Added in 079925cce1d0 ("net: allow SO_MARK with CAP_NET_RAW") in v5.17.
> 
> > > Signed-off-by: Petr Vorel <pvorel@...e.cz>
> 
> > Patch applied.  Thanks!
> 
> Thank you! BTW I don't see this patch in git tree [1], maybe you just haven't
> push yet.

That's it.  I'm first pushing them to a 'contrib' branch (similar to
Linux 'next') in my own server[1], and after one day or so I push to
master.  That buffering allows me to catch some mistakes.

[1]:  <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/?h=contrib>

	$ git log --all --graph --oneline -10
	* 0c118822f (alx/contrib, contrib) open.2: srcfix
	* 24347d22a syscalls.2: ffix
	* 9e04cb40f mremap.2: wfix
	* 3a271d5b8 fts.3, div_t.3type: ffix
	* 527f31b9f socket.7: Mention CAP_NET_RAW on SO_MARK
	| * 71c25f15d (alx/MR, MR) man*/: ffix (MR.sed)
	|/  
	* d82ce270c (HEAD -> master, korg/master, alx/main, main) locale.5: tfix
	* f65154cba cpuid.4: Note which CPUs don't support CPUID and what happens
	* f98168310 sched_getcpu.3: tfix
	* 26cdb3ebb faccessat(2), utimensat(2): Document AT_EMPTY_PATH flag

I'll push in a moment to master.

Have a lovely day,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ