[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080713104617.GA79@tv-sign.ru>
Date: Sun, 13 Jul 2008 14:46:17 +0400
From: Oleg Nesterov <oleg@...sign.ru>
To: Denys Vlasenko <vda.linux@...glemail.com>
Cc: T?r?k Edwin <edwintorok@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Roland McGrath <roland@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Elias Oltmanns <eo@...ensachen.de>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] x86_64: fix delayed signals
On 07/12, Denys Vlasenko wrote:
>
> On Saturday 12 July 2008 22:26, T?r?k Edwin wrote:
> > A bit off-topic, but something I noticed during the tests:
> > In my original test I have rm-ed the files right after launching dd in
> > the background, yet it still continued to write to the disk.
> > I can understand that if the file is opened O_RDWR, you might seek back
> > and read what you wrote, so Linux needs to actually do the write,
> > but why does it insist on writing to the disk, on a file opened with
> > O_WRONLY, after the file itself got unlinked?
>
> Because process can do
>
> fcntl(fd, F_SETFL, fcntl(fd, F_GETFL) | O_RDWR)
Is it?
SETFL_MASK doesn't have O_RDWR, and in any case setfl() changes ->f_flags,
not ->f_mode.
Oleg.
--
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/
Powered by blists - more mailing lists