linux-kernel - Re: [PATCH] x86_64: fix delayed signals

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200807131845.m6DIjrX03598@inv.it.uc3m.es>
Date:	Sun, 13 Jul 2008 20:45:53 +0200
From:	"Peter T. Breuer" <ptb@....it.uc3m.es>
To:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: fix delayed signals

In article <alpine.LFD.1.10.0807131121430.2959@...dy.linux-foundation.org> you wrote:
> Anyway, I misunderstood Edwins idea to actually throw away the writes if 
> the file isn't linked anywhere and is only open for writing. I guess we 

I don't understand it.  The process can still clone itself and its
children may want to look at what it has written (maybe there's too much
file to fit in an mmap all at once) via the same file descriptor.  Come
to that, the process itself may want to look at what it's written!

Saving memory is the idea behind writing to disk sometimes. Unlinking
your target is sensible if you want to keep your thoughts private ..

Peter
--
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/