linux-kernel - Re: [PATCH] /dev/mem: Fix wrong error on accessing beyond valid memory addresses.

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: <2018804336.46235.1321305700330.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
Date:	Mon, 14 Nov 2011 13:21:40 -0800 (PST)
From:	Andrei Warkentin <awarkentin@...are.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] /dev/mem: Fix wrong error on accessing beyond valid
 memory addresses.

Hi Peter,

----- Original Message -----
> From: "Andrei Warkentin" <andreiw@...are.com>
> To: linux-kernel@...r.kernel.org
> Cc: "Andrei Warkentin" <andreiw@...are.com>, "H. Peter Anvin" <hpa@...or.com>
> Sent: Wednesday, November 9, 2011 6:31:19 PM
> Subject: [PATCH] /dev/mem: Fix wrong error on accessing beyond valid memory addresses.
> 
> Currently this returns -EFAULT, but it really should be returning 0,
> as in - 0 bytes read or written. This is what you would get by
> opening a block device, seeking to the end, and trying to read
> something. Additionally, make lseek() check the sought-to offset
> to pass the valid_phys_addr_range test.
> 
> Cc: H. Peter Anvin <hpa@...or.com>
> Signed-off-by: Andrei Warkentin <andreiw@...are.com>
> ---

I know you're very busy, but I was wondering if you could
give your two cents on this change. This change grew from
our discussion on LKML last week.

Thanks ahead,
A
--
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/