linux-kernel - Re: [PATCH 2/2] proc: fix PAGE_SIZE limit of /proc/$PID/cmdline

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: <20150528120031.GM17625@uranus.sw.swsoft.com>
Date:	Thu, 28 May 2015 15:00:31 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jarod Wilson <jarod@...hat.com>,
	Jan Stancek <jstancek@...hat.com>
Subject: Re: [PATCH 2/2] proc: fix PAGE_SIZE limit of /proc/$PID/cmdline

On Thu, May 28, 2015 at 02:35:07PM +0300, Cyrill Gorcunov wrote:
> On Thu, May 28, 2015 at 02:14:41PM +0300, Alexey Dobriyan wrote:
> > >>
> > >> It is snapshot w.r.t getting both pairs not snapshot w.r.t atomicity or
> > >> something (unsigned long access is atomic after all). Once down_write()
> > >> is used in the other place, it even becomes obviously correct code!
> > >
> > > Not at all. It is correct if and only if you're operating under lock
> > > taken, once you fetch the pair and left the lock it simply local copies
> > > of values the descriptor had when lock was taken.
> > 
> > Yes, and?
> > 
> > You do not complain that signal statistics is collected
> > under sighand lock but printed for /proc/*/status without, do you?
> 

After thinking more, right, you're correct, sorry for noise.
--
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/