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: <20240517074742.24709-1-kuniyu@amazon.com>
Date: Fri, 17 May 2024 16:47:42 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <mhal@...x.co>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
	<kuniyu@...zon.com>, <netdev@...r.kernel.org>, <pabeni@...hat.com>,
	<shuah@...nel.org>
Subject: Re: [PATCH net v2 1/2] af_unix: Fix garbage collection of embryos carrying OOB with SCM_RIGHTS

From: Michal Luczaj <mhal@...x.co>
Date: Fri, 17 May 2024 07:59:16 +0200
> One question: git send-email automatically adds my Signed-off-by to your
> patch (patch 2/2 in this series). Should I leave it that way?

SOB is usually added by someone who changed the diff or merged it.

I think it would be better not to add it if not intended.  At least
on my laptop, it does not add SOB automatically.

FWIW, my command is like

  git send-email --annotate --cover-letter --thread --no-chain-reply-to \
  --subject-prefix "PATCH v1 net-next" \
  --to "" \
  --cc "" \
  --cc netdev@...r.kernel.org \
  --batch-size 1 --relogin-delay 15 --dry-run HEAD~10

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ