linux-kernel - Re: [PATCH] proc: advertise new restrictions on /proc/*/maps & /proc/*/smaps

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]

Date:	Fri, 4 Jan 2008 11:38:47 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Guillaume Chazarain <guichaz@...oo.fr>
Cc:	Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] proc: advertise new restrictions on /proc/*/maps & /proc/*/smaps

On Fri, Jan 04, 2008 at 12:15:02PM +0100, Guillaume Chazarain wrote:
> Al Viro <viro@...IV.linux.org.uk> wrote:
> 
> > The whole point is that we have to reject it at read() time, not open()
> > time.
> 
> Yes, my patch was a complement to yours to propagate the -EPERM in easy
> cases. As you noted it added restrictions on reading /proc/*/maps, even
> though I found them acceptable.
> 
> How about this instead?
> 
> Maybe you'd prefer to propagate the actual -EPERM from
> __ptrace_may_attach but that would be more invasive.
> 
> Sidenote: do you think a sparse annotation to check IS_ERR/PTR_ERR
> usage would make sense?
> 
> proc: return -EPERM when preventing read of /proc/*/maps
> 
> Return an error instead of successfully reading an empty file.

You are overcomplicating it - if ->start() returns ERR_PTR(), it's over;
read() will fail with that error and that's it.  No need to mess with
->next(), etc. - it'll never see that ERR_PTR(-EPERM).  Drop these chunks
and you've got an ACK...
--
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/