* Anton Altaparmakov <[email protected]> wrote:
> An example is the potential deadlock in generic buffered file write
> where we fault in a page via fault_in_pages_readable() but there is
> nothing to guarantee that page will not go away between us doing this
> and us using the page.
isnt this solved by:
commit 6527c2bdf1f833cc18e8f42bd97973d583e4aa83
Author: Vladimir V. Saveliev <[email protected]>
Date: Tue Jun 27 02:53:57 2006 -0700
[PATCH] generic_file_buffered_write(): deadlock on vectored write
?
if not, do you have any description of the problem or a link to previous
discussion[s] outlining the problem? To me it appears this is a kernel
bug where we simply dropped the ball to fix it. I personally dont find
it acceptable to have deadlocks in the kernel, where all that is needed
to trigger it is "high i/o loads", no matter how hard it is to fix the
deadlock.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
