Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jul 2006 15:57:28 +0200
From:      Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To:        Mykola Stryebkov <mykola.stryebkov@gmail.com>, hackers@freebsd.org
Subject:   Re: fork inside ip_input
Message-ID:  <44B7A2C8.7050407@fs.ei.tum.de>
In-Reply-To: <20060714134953.GA2404@taran.infoua.com.ua>
References:  <20060714134953.GA2404@taran.infoua.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig915844A8B1C460A79C610A45
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Mykola Stryebkov wrote:
> Hi all.
>=20
> Have a strange question: is it possible to create new process (using
> fork or fork1) from inside of ip_input()?

i don't think so.

> In kernel sources i found example of using fork1 in init_main.c but
> looking into ip_input.c i do not understand where i can get pointers to=

> a thread and parent process to pass it into fork1.

only a process can fork, but ip_input is run from interrupt, not in a pro=
cess context.  which process do you want to fork anyways?

cheers
  simon

--=20
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low =E2=82=AC=E2=82=AC=E2=82=AC NOW!1  +++=
      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \


--------------enig915844A8B1C460A79C610A45
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (DragonFly)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEt6LKr5S+dk6z85oRAqb4AKDGfxjm+5LxNtNsrCdVce0bcHB7eQCdGx6J
UPjQF+Pvw2SedW0MKKgr0hw=
=GHI5
-----END PGP SIGNATURE-----

--------------enig915844A8B1C460A79C610A45--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B7A2C8.7050407>