Re: Locking Memory Question

2015-07-29 Thread K. Macy
>> >> Im not clear how I'd do that. the data being passed up from the kernel is a >> variable size. To use copyout I'd have to pass a >> pointer with a static buffer, right? > > Correct, you can pass along the size, and if it's not large enough > try again... Less than ideal... > >> Is there a way

Re: Locking Memory Question

2015-07-29 Thread John-Mark Gurney
Laurie Jennings wrote this message on Wed, Jul 29, 2015 at 17:52 -0700: > > On Wed, 7/29/15, John-Mark Gurney wrote: > > Subject: Re: Locking Memory Question > To: "Laurie Jennings" > Cc: "John Baldwin" , freebsd-net@freebsd.org > Date: Wednesday,

[Bug 197535] [re] [panic] if_re (Realtek 8168) causes memory write after free and kernel panic

2015-07-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535 Marius Strobl changed: What|Removed |Added Resolution|--- |FIXED Status|New

Re: Locking Memory Question

2015-07-29 Thread John Baldwin
On Wednesday, July 29, 2015 03:26:46 PM Laurie Jennings wrote: > > I have a problem and I can't quite figure out where to look. This is what Im > doing: > > I have an IOCTL to read a block of data, but the data is too large to return > via ioctl. So to get the data, > I allocate a block in a ke

Re: Locking Memory Question

2015-07-29 Thread Laurie Jennings via freebsd-net
On Wed, 7/29/15, John-Mark Gurney wrote: Subject: Re: Locking Memory Question To: "Laurie Jennings" Cc: "John Baldwin" , freebsd-net@freebsd.org Date: Wednesday, July 29, 2015, 7:25 PM Laurie Jennings via freebsd-net wrote this message on Wed

Re: Locking Memory Question

2015-07-29 Thread John-Mark Gurney
Laurie Jennings via freebsd-net wrote this message on Wed, Jul 29, 2015 at 15:26 -0700: > > I have a problem and I can't quite figure out where to look. This is what Im > doing: > > I have an IOCTL to read a block of data, but the data is too large to return > via ioctl. So to get the data, >

Locking Memory Question

2015-07-29 Thread Laurie Jennings via freebsd-net
I have a problem and I can't quite figure out where to look. This is what Im doing: I have an IOCTL to read a block of data, but the data is too large to return via ioctl. So to get the data, I allocate a block in a kernel module: foo = malloc(1024000,M_DEVBUF,M_WAITOK); I pass up a pointer

Locking Memory Question

2015-07-29 Thread Laurie Jennings via freebsd-net
___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 201947] Panics in if_bfe under certain loads types (reproducible with rtorrent)

2015-07-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201947 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org -- You are

Re: remove IPsec SKIPJACK support...

2015-07-29 Thread John-Mark Gurney
John-Mark Gurney wrote this message on Wed, Jul 29, 2015 at 09:11 -0700: > George Neville-Neil wrote this message on Wed, Jul 29, 2015 at 10:35 -0400: > > That's fine so long as its removed in HEAD now, and then the warning can > > go into 10 aka 10.3. > > As I said, setkey doesn't support it.. a

Re: remove IPsec SKIPJACK support...

2015-07-29 Thread John-Mark Gurney
George Neville-Neil wrote this message on Wed, Jul 29, 2015 at 10:35 -0400: > That's fine so long as its removed in HEAD now, and then the warning can > go into 10 aka 10.3. As I said, setkey doesn't support it.. and I looked at the ports for racoon2 and strongswan (has it in their library, but,

[Differential] [Commented On] D1944: PF and VIMAGE fixes

2015-07-29 Thread rodrigc (Craig Rodrigues)
rodrigc added a comment. @glebius: Nikos updated the patch. Can you review it? REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, trociny, kristof, gnn, zec, rodrigc, glebius, eri Cc: farr

Re: remove IPsec SKIPJACK support...

2015-07-29 Thread George Neville-Neil
That's fine so long as its removed in HEAD now, and then the warning can go into 10 aka 10.3. Best, George On 28 Jul 2015, at 13:25, Adrian Chadd wrote: Hi, I'd put together a deprecation plan, which starts with the kernel warning that this stuff is being removed, MFC that to stable/10 and