Re: KSE was Re: open/close/ioctl api change?
- From: Julian Elischer <julian@xxxxxxxxxxxx>
- Date: Mon, 25 Jun 2007 12:20:06 -0700
Danny Braniss wrote:
Danny Braniss wrote:why? I'm compiling outside the source tree.even so it shouldnt' happen..actually it's the struct thread *tp where my problems are,found the problem, 'option KSE' which is defined now in DEFAULTS,
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.
and i'm compiling a module! which does not include DEFAULTS!
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.
there should be no place in the source at any time where a thread that is not on the free list could have a td_proc of NULL.
it doesn't matter about where a module came from etc.. the fact that
it happened is a bug somewhere.
danny
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- References:
- KSE was Re: open/close/ioctl api change?
- From: Danny Braniss
- Re: KSE was Re: open/close/ioctl api change?
- From: Julian Elischer
- Re: KSE was Re: open/close/ioctl api change?
- From: Danny Braniss
- KSE was Re: open/close/ioctl api change?
- Prev by Date: Re: KSE was Re: open/close/ioctl api change?
- Next by Date: Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64
- 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
|
|