Do not allocate my_type (in general, big data structures)
on kernel stack (e.g, use malloc(9)).
Adam wrote:
Hi, I am writing a custom system call that needs to transfer 16kb of
data from the kernel to userspace. I am transferring the data out of
the kernel by using copyout. This seems to wor
On Thu, Apr 24, 2008 at 1:24 AM, Bakul Shah <[EMAIL PROTECTED]> wrote:
> On Wed, 23 Apr 2008 23:34:41 PDT "Garrett Cooper" <[EMAIL PROTECTED]>
> wrote:
> > I know that dereferencing a NULL pointer yields a segfault because
> address 0
> > can't be accessed.
> >
> > The point is that I didn't real
On Fri, Apr 25, 2008 at 9:59 AM, Adam <[EMAIL PROTECTED]> wrote:
> Hi, I am writing a custom system call that needs to transfer 16kb of data
> from the kernel to userspace. I am transferring the data out of the kernel
> by using copyout. This seems to work for a small struct of data < 4k.
>
> int
On Fri, Apr 25, 2008 at 09:59:55AM -0400, Adam wrote:
> Hi, I am writing a custom system call that needs to transfer 16kb of data
> from the kernel to userspace. I am transferring the data out of the kernel
> by using copyout. This seems to work for a small struct of data < 4k.
You are not allo
Hi, I am writing a custom system call that needs to transfer 16kb of
data from the kernel to userspace. I am transferring the data out of
the kernel by using copyout. This seems to work for a small struct of
data < 4k.
int my_system_call(struct thread *td, struct my_system_call_args *uap)
on 25/04/2008 17:36 Kostik Belousov said the following:
The malloc and free cannot be called while holding dev_mtx, this causes
the LORs. Please, look at the rev. 1.207, 1.210 of the kern/kern_conf.c
for the workarounds for the malloc issues. It seems that you may abuse the
dev_unlock_and_free()
On Fri, Apr 25, 2008 at 05:12:12PM +0300, Andriy Gapon wrote:
> on 25/04/2008 12:50 Kostik Belousov said the following:
> >Did you run this with WITNESS ?
> >
> >You put the whole devctl_notify() call under the dev_mtx. This includes
> >the malloc(), PROC_LOCK() and signalling, and some internal de
on 25/04/2008 12:50 Kostik Belousov said the following:
Did you run this with WITNESS ?
You put the whole devctl_notify() call under the dev_mtx. This includes
the malloc(), PROC_LOCK() and signalling, and some internal devctl_queue()
stuff. This is wrong.
Kostik,
I tried this patch only with
Hi Przemek,
If you need any help at all, feel free to bug me :)
We're very excited about the FreeBSD port to Efika.
--
Matt Sealey <[EMAIL PROTECTED]>
Genesi, Manager, Developer Relations
vi0 wrote:
Hello everybody!!!
My name is Przemek Witaszczyk and I am one of those very happy
FreeBSD GSo
Quoting David Forsythe, who wrote on Thu, Apr 24, 2008 at 07:46:02PM -0400 ..
> Hello everybody,
>
> My name is David Forsythe and I'll be working on allowing parallel builds in
> the
> ports collection for Summer of Code this year. I'm a second year student at
> the
> University of Maryland, C
On Thu, 24 Apr 2008 19:46:02 -0400
David Forsythe <[EMAIL PROTECTED]> wrote:
> My name is David Forsythe and I'll be working on allowing parallel builds in
> the
> ports collection for Summer of Code this year.
>
This would definitely be of benefit! Good luck.
---
Gary Jennejohn
_
On Fri, Apr 25, 2008 at 12:35:26AM +0300, Andriy Gapon wrote:
>
> I decided to do it in devfs_devs.c because there are less entry points
> there and the code is much simpler (you know: aliases, clones).
> I also had to add !cold condition, because apparently we have devices
> created so early in t
On Thu, 24 Apr 2008 19:47:14 +0200
vi0 <[EMAIL PROTECTED]> mentioned:
> Hello everybody!!!
>
> My name is Przemek Witaszczyk and I am one of those very happy
> FreeBSD GSoCers of 2008:)
>
> I am 25 years old and I come from Polad. Currently I'm working on
> my PhD in the field of theoretical phy
13 matches
Mail list logo
