Re: KSE was Re: open/close/ioctl api change?
- From: Danny Braniss <danny@xxxxxxxxxxxxx>
- Date: Mon, 25 Jun 2007 22:12:04 +0300
Danny Braniss wrote:why? I'm compiling outside the source tree.
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.
found the problem, 'option KSE' which is defined now in DEFAULTS,
and i'm compiling a module! which does not include DEFAULTS!
even so it shouldnt' happen..
I agree that it shouldn't, specially, since it took me a long
time to find the problem :-), but I can't see how config options
can be exported. Unless, the make file is made aware of the KERNCONF file.
danny
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: KSE was Re: open/close/ioctl api change?
- From: Julian Elischer
- Re: KSE was Re: open/close/ioctl api change?
- References:
- KSE was Re: open/close/ioctl api change?
- From: Danny Braniss
- Re: KSE was Re: open/close/ioctl api change?
- From: Julian Elischer
- KSE was Re: open/close/ioctl api change?
- Prev by Date: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64
- Next by Date: Re: KSE was Re: open/close/ioctl api change?
- Previous by thread: Re: KSE was Re: open/close/ioctl api change?
- Next by thread: Re: KSE was Re: open/close/ioctl api change?
- Index(es):
Relevant Pages
|
|