> > Its potentially going to stop umounts, and file write accesses.
> >
> > If you think this is the case, the following should find which device
> > the problem is on (untested)
[...]
> Therefore, I suspect pipe.c:do_pipe() and socket.c:get_fd().
As I suspected, pipes and sockets are the evil ones. Evidence:
put_write_access: i_writecount = 0, i_mode = 140000 i_dev: 0 i_ino: 488
put_write_access: i_writecount = 0, i_mode = 140000 i_dev: 0 i_ino: 489
put_write_access: i_writecount = 0, i_mode = 140000 i_dev: 0 i_ino: 490
put_write_access: i_writecount = 0, i_mode = 140000 i_dev: 0 i_ino: 492
put_write_access: i_writecount = 0, i_mode = 140000 i_dev: 0 i_ino: 491
put_write_access: i_writecount = 0, i_mode = 10600 i_dev: 0 i_ino: 493
put_write_access: i_writecount = 0, i_mode = 10600 i_dev: 0 i_ino: 494
put_write_access: i_writecount = 0, i_mode = 10600 i_dev: 0 i_ino: 495
put_write_access: i_writecount = 0, i_mode = 10600 i_dev: 0 i_ino: 496
put_write_access: i_writecount = 0, i_mode = 10600 i_dev: 0 i_ino: 498
/Magnus
[EMAIL PROTECTED]
