Re: threads and kill-buffer

[Sam Steingold <sds@gnu.org>]

> * Eli Zaretskii <ryvm@tah.bet> [2012-09-05 05:53:56 +0300]:
>
> How about letting kill-buffer succeed, but delay the actual deletion
> of the buffer until no thread has it as current, like what Posix
> filesystems do with file deletion?

I am not sure that Posix file systems do this "by design" and not as a
side effect of an implementation detail.

At any rate, I don't think this behavior is very useful.

It is a certain way to lose data: imagine thread T1 moving data from
buffer B1 to buffer B2 and thread T2 killing one of these buffers.
Killing B1 is fine, but killing B2 will lose data. Note that being the
current buffer of another thread is an insufficient protection because a
thread may be writing to several buffers and only one of them may be
current to it, so a thread should be able to mark a buffer as used by
it, so that an attempt to kill a buffer used by a live thread would
result in an exception.


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://palestinefacts.org http://www.memritv.org
http://jihadwatch.org http://honestreporting.com
When we break the law, they fine us, when we comply, they tax us.