public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Ammar Faizi <[email protected]>,
	Tea Inside Mailing List <[email protected]>,
	Michael Arminto <[email protected]>,
	Louvian Lyndal <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH teavpn2 0/3] teavpn2 fixes
Date: Fri, 27 May 2022 07:14:16 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Fri, 27 May 2022 00:02:24 +0000, Alviro Iskandar Setiawan wrote:
> I have a few TeaVPN2 fixes, please review. 3 patches below:
> 
> ### Patch 1
> The calloc() function from libc sets the @errno variable to ENOMEM
> when overflow, not to EOVERFLOW. Change it to ENOMEM to follow libc
> error code.
> 
> [...]

Applied, thanks!

[1/3] allocator: Fix `@errno` value when overflow
      commit: 3541908d4fe36522b6fbffec6d8455a824c89237
[2/3] net: iface: Fix a potential NULL pointer dereference
      commit: 7c9b07476d86fb27df835d977c07319954661a10
[3/3] arch/linux: syscall: Fix retval checking in libc syscall
      commit: c157b7221901d0b2f2ede5ab0f01471ecac91fed

Best regards,
-- 
Ammar Faizi


      parent reply	other threads:[~2022-05-27  0:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  0:02 [PATCH teavpn2 0/3] teavpn2 fixes Alviro Iskandar Setiawan
2022-05-27  0:02 ` [PATCH teavpn2 1/3] allocator: Fix `@errno` value when overflow Alviro Iskandar Setiawan
2022-05-27  0:02 ` [PATCH teavpn2 2/3] net: iface: Fix a potential NULL pointer dereference Alviro Iskandar Setiawan
2022-05-27  0:02 ` [PATCH teavpn2 3/3] arch/linux: syscall: Fix retval checking in libc syscall Alviro Iskandar Setiawan
2022-05-27  0:14 ` Ammar Faizi [this message]

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=165361029468.375291.11178308260252768138.b4-ty@gnuweeb.org \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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