linux-kernel - Re: regarding mprotect() implementation in 2.6.26 kernel

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] [day] [month] [year] [list]

Message-ID: <9debc4410808040418u25f49436r4bb689f04f792564@mail.gmail.com>
Date:	Mon, 4 Aug 2008 16:48:38 +0530
From:	"Maxin John" <maxin.john@...il.com>
To:	"Michael Kerrisk" <mtk.manpages@...glemail.com>
Cc:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	linux-kernel@...r.kernel.org, ak@....de, mtk.manpages@...il.com,
	shields@...bel.org, hirofumi@...l.parknet.co.jp
Subject: Re: regarding mprotect() implementation in 2.6.26 kernel

Dear Michael,


> So, after a quick search, it looks as though in kernels before 2.4.19,
> the EFAULT error resulted instead of ENOMEM for this case.  Does that
> sound right to you?

 Yes, I do agree with you. After Linux Kernel version 2.4.19 , the
ENOMEM error resulted instead of EFAULT in the mprotect().

Regards,

Maxin B. John
Bangalore, India
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/