From: Rusty Russell <rusty@rustcorp.com.au>
To: davem@redhat.com, kuznet@ms2.inr.ac.ru, sfr@canb.auug.org.au
Cc: linux-kernel@vger.kernel.org
Subject: Moving fasync_struct into struct file?
Date: Tue, 19 Feb 2002 18:18:12 +1100
Message-Id: <E16d4XU-0003VI-00@wagner.rustcorp.com.au>
Sender: linux-kernel-owner@vger.kernel.org

Hi guys,

	Stephen Rothwell pointed out that if you set up SIGIO from an
fd, fork, and exit, and PIDs wrap, the new process may be clobbered by
the SIGIO.  IMVHO the best way to clean this up is to check the
fasync_list in sys_close, and if pid == filp->f_owner.pid and fd ==
fasync_list->fa_fd, unregister the SIGIO.

	This means we need a move the "struct fasync_struct
fasync_list" into struct file (up from all the subsystems which use
it, eg. struct socket).

See any problems with this?
Rusty. 
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/