Hi
I am getting kernel messages = protocol is buggy, dev eth0 in my
kernel while calling dev_queue_xmit(skb);. The packet is successfully
tranmitted on the wire but these messages are keep coming on the console.
I am not sure what is the exact modification needed to avoid these kernel
On 03/17/13 17:07, Robert P. J. Day wrote:
as i don't want to seem like i'm spamming this list with notes about
new, posted kernel tutorials, people who want to stay on top of these
are welcome to follow me on twitter at @rpjday. everything written and
posted will be freely available
FYI___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Sengottuvelan S sengottuvela...@gmail.com writes:
Hi
I am getting kernel messages = protocol is buggy, dev eth0 in my
kernel while calling dev_queue_xmit(skb);. The packet is successfully
tranmitted on the wire but these messages are keep coming on the console.
I am not sure what is
Hi ...
On Tue, Mar 19, 2013 at 12:28 PM, Kumar amit mehta gmate.a...@gmail.com wrote:
grep for copy_from_user_overflow gives me this:
amit@ubuntu:~/linux-next/linux-next$ grep -ri copy_from_user_overflow *
arch/s390/include/asm/uaccess.h:extern void copy_from_user_overflow(void)
Hi Niroj
Please see inlined answer below...
On Mon, Mar 18, 2013 at 5:28 PM, Niroj Pokhrel nirojpokh...@gmail.com wrote:
Hi all,
As I have read, whenever we execute a program, the memory is allocated in
different sections viz stack, text and data segment.
Yup, that is correct
But,
On Tue, Mar 19, 2013 at 8:27 PM, Mulyadi Santosa
mulyadi.sant...@gmail.comwrote:
Hi Niroj
Please see inlined answer below...
On Mon, Mar 18, 2013 at 5:28 PM, Niroj Pokhrel nirojpokh...@gmail.com
wrote:
Hi all,
As I have read, whenever we execute a program, the memory is allocated in
Hi Folks,
I'm trying to understand the linux way of doing things, so as to write
code which will be easier for experienced linux kernel people to
understand. Yesterday I wound up in a 3 engineer discussion about
something conceptually simple, that just didn't want to be done with
the tools at
Quoting Arlie Stephens ar...@worldash.org:
Hi Folks,
I'm trying to understand the linux way of doing things, so as to write
code which will be easier for experienced linux kernel people to
understand. Yesterday I wound up in a 3 engineer discussion about
something conceptually simple, that
Hi Arlie,
On Tue, Mar 19, 2013 at 8:34 AM, Arlie Stephens ar...@worldash.org wrote:
Hi Folks,
I'm trying to understand the linux way of doing things, so as to write
code which will be easier for experienced linux kernel people to
understand. Yesterday I wound up in a 3 engineer discussion
On Tue, 19 Mar 2013 20:41:55 +0530, Niroj Pokhrel said:
#includestdio.h
int main()
{
while(1)
{
}
return 0;
}
I don't understand where does mmap or malloc come in to play in this code.
Unless you linked it statically, a lot of stuff happens before you ever
get to main()
On Tue, Mar 19, 2013 at 3:53 PM, Dave Hylands dhyla...@gmail.com wrote:
Hi Arlie,
On Tue, Mar 19, 2013 at 8:34 AM, Arlie Stephens ar...@worldash.org
wrote:
Hi Folks,
I'm trying to understand the linux way of doing things, so as to write
code which will be easier for experienced
Hi Dave,
Thank you very much.
On Mar 19 2013, Dave Hylands wrote:
Hi Arlie,
[SNIP]
So the real secret is that it's a circular list with a dummy node. This
dummy node just has head/tail pointers and nothing else.
It's good to have confirmation of this.
So when you're advancing
Quoting Arlie Stephens ar...@worldash.org:
Interestingly, part of the debate yesterday probably resulted from one
engineer having Love's 2nd edition, and me having his 3rd
edition. Apparently RPDay pointed out some problems to Love which
resulted in him changing his linked list discussion in
Quoting Robert P. J. Day rpj...@crashcourse.ca:
Quoting Arlie Stephens ar...@worldash.org:
Interestingly, part of the debate yesterday probably resulted from one
engineer having Love's 2nd edition, and me having his 3rd
edition. Apparently RPDay pointed out some problems to Love which
Hi Robert,
Thank you very much - for your web pages as well as for your responses
in this thread.
On Mar 19 2013, Robert P. J. Day wrote:
Oh, crap, I just remembered that even Robert Love's 3rd edition of
Linux Kernel Development (aka LKD3) isn't 100% correct WRT linked
lists. A while
On Tue, Mar 19, 2013 at 8:50 PM, Victor Buciuc victor.buc...@gmail.com wrote:
On Tue, Mar 19, 2013 at 5:34 PM, Arlie Stephens ar...@worldash.org wrote:
Hi Folks,
I'm trying to understand the linux way of doing things, so as to write
code which will be easier for experienced linux kernel
On Tue, 19 Mar 2013, Arlie Stephens wrote:
Hi Robert,
Thank you very much - for your web pages as well as for your responses
in this thread.
On Mar 19 2013, Robert P. J. Day wrote:
Oh, crap, I just remembered that even Robert Love's 3rd edition of
Linux Kernel Development (aka LKD3)
On Tue, 19 Mar 2013, ishare wrote:
/**
* module_init() - driver initialization entry point
* @x: function to be run at kernel boot time or module insertion
*
* module_init() will either be called during do_initcalls() (if
* builtin) or at module insertion time (if a module).
19 matches
Mail list logo
