James Smart wrote: > > > Patrick McHardy wrote: > >> This might be problematic, since there is a shared receive-queue in >> the kernel netlink message might get processed in the context of >> a different process. I didn't find any spots where ISCSI passes >> pointers over netlink, can you point me to it? > > > Please explain... Would the pid be set erroneously as well ? Ignoring > the kernel-user space pointer issue, we're going to have a tight > pid + request_id relationship being maintained across multiple messages. > We'll also be depending on the pid events for clean up if an app dies. > So I hope pid is consistent.
The PID contained in the netlink message itself is correct, current->pid might not be. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
