Re: ipfilter cannot be build within because warning's are present

From: Victor M. Blood <freebsd_at_masm.elcom.ru>
Date: Thu, 18 Oct 2007 17:24:32 +0400
On 18.10.2007, Max Laier wrote:
> On Thursday 18 October 2007, Victor M. Blood wrote:
>> On 18.10.2007, Max Laier wrote:
>> > On Wednesday 17 October 2007, Victor M. Blood wrote:
>> >> Hi, All.
>> >>
>> >> I try to use options in kernel instead of a module build of the
>> >> ipfilter and got error then kernel builds.
>> >>
>> >> I'm edit files: fil.c, ip_auth.h, ip_auth.h, ip_log.c ip_compat.h
>> >> and correct #ifdef statament :) no more warnings...
>> >
>> > ipf is likely broken anyway.  See thread: "7.0 CURRENT, need help
>> > with panic: Trying sleep, but thread marked as sleeping prohibited"
>> > on this ML a few days back.  That this warning went unnoticed tells
>> > you something, too.
>>
>> New version, new problems, no more to say) few days back I have panic
>> with ip filter, now it seems as worked, after upgrade.
>>
>> #ipf -V
>> ipf: IP Filter: v4.1.27 (404)
>> Kernel: IP Filter: v4.1.27
>> Running: yes
>> Log Flags: 0 = none set
>> Default: block all, Logging: available
>> Active list: 0
>> Feature mask: 0xe

> Is this with a WITNESS/INVARIANTS enabled kernel?
yes, all debug option are on, and WITNESS/INVARIANTS too
> From a quick glance at
> the code you should see warnings on the ioctl path as there are copy 
> operations to/from userland with the lock held.
Hmm... I don't understand there I can find it, may be exist way to
fix. Make results in attach.

> Moving to rw_locks is the right direction, but the config path is still
> broken.
I send all building and patch results to Darren Reed...

-- 
With all regards, Victor M. Blood.   mailto: freebsd_at_masm.elcom.ru
FTN: 2:5024/1.95_at_Fidonet.org, ICQ#3567656


Received on Thu Oct 18 2007 - 11:24:59 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:19 UTC