Re: open/close/ioctl api change?

5 msg	ZFS deadlocks or panics
1 msg	TCP Spurious RST, segment rejected
1 msg	how to handle name clashes in linux/freebsd ker...
10 msg	Is this reasonable ?
11 msg	[PATCH] Machine Check Architecture on amd64
5 msg	Issues with 'xl0' keeping link
2 msg	Re: The relation between %fs and fs base
20 msg	[head tinderbox] failure on amd64/amd64
27 msg	[head tinderbox] failure on i386/pc98
1 msg	ZFS and Jails (dataset does not exist)
2 msg	RE: unionfs and tmpfs?
1 msg	binutils/gas compilation problems on i386.
19 msg	Silent gcc 4.2.0 loop optimization bug with -O2
3 msg	Problem compiling -CURRENT/OpenSSL
6 msg	KSE was Re: open/close/ioctl api change?

open/close/ioctl api change?
\ Danny Braniss (25 Jun 2007)
. \ Kostik Belousov (25 Jun 2007)

4 msg	ZFS and gmirror
4 msg	ZFS questions
3 msg	Q) lockf(flock?) on -current (amd64)
3 msg	options IPI_PREEMPTION and PREEMPTION in 7.0 AMD64

Subject:	Re: open/close/ioctl api change?
Group:	Freebsd-current
From:	Kostik Belousov
Date:	25 Jun 2007

On Mon, Jun 25, 2007 at 02:49:29PM +0300, Danny Braniss wrote:
> actually it's the struct thread *tp where my problems are,
> this code works fine under 6.2, and did work till some days ago under current.
>
> static int
> iscsi_open(struct cdev *dev, int flags, int otype, struct thread *td)
> {
> ...
> debug(3, "td->td_proc=%p", td->td_proc);
> debug(3, "td->td_proc->p_pid=%d pid=%d",
> td->td_proc->p_pid, curproc->p_pid);
> ...
>
> the first debug prints out td->td_proc=0 and the next one panics.

I think you shall start with posting full panic information, and ddb/kgdb
output for the trace.

There have been some change in KPI (I assume you example is about in-kernel
interfaces), but it shall not affect d_open() driver methods.