Re: [PATCH] INITEST: Documentation: Explains how INITEST works.

2016-09-29 Thread Bjørn Mork 
Amit Kumar  writes:

> Signed-off-by: Amit Kumar 
>
> This is a test patch.
> Is this patch in right format?
> ---
>  Documentation/initest.txt | 7 +++
>  1 file changed, 7 insertions(+)
>  create mode 100644 Documentation/initest.txt
>
> diff --git a/Documentation/initest.txt b/Documentation/initest.txt
> new file mode 100644
> index 000..eed4124
> --- /dev/null
> +++ b/Documentation/initest.txt
> @@ -0,0 +1,7 @@
> +INITEST
> +
> +1) This is the same user space program /sbin/init, but for the purpose of 
> testing kernel system calls.
> +
> +2) It will also use testing drivers to test internal kernel API.
> +
> +3) This is a test patch.


Looks pretty good.  But a few more things to keep in mind:

1) There should be *some* body text describing the patch, even for a very
   basic change which is explained in full in subject.  This goes first
   in the body, separated from the tags with a single empty line.

2) Signed-off-by and other tags go at the end of the body, right before
  the "---" separator.  Don't put anything between the SOB and the
  separator.  I realize that this was just a question that you wouldn't
  make part of the submitted patch but still: It broke your example...

3) There is a place for questions about the patch which you do not want
  to be part of the commit message: Right After the first "---"
  separator.  Anything yout put there will be ignored by git when the
  patch is applied, just like the diffstat git includes by itself.

  This is useful if you need to explain something to the maintainer
  regarding how to apply the patch, or if ytou have questions about it
  which are irrelevant if applied.



So the end result would be:


Subject: [PATCH] INITEST: Documentation: Explains how INITEST works.

This is a test patch.

Signed-off-by: Amit Kumar 
---
Is this patch in right format?


Documentation/initest.txt | 7 +++
1 file changed, 7 insertions(+)
create mode 100644 Documentation/initest.txt

diff --git a/Documentation/initest.txt b/Documentation/initest.txt
[etc]



Bjørn

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: [PATCH] INITEST: Documentation: Explains how INITEST works.

2016-09-29 Thread Greg KH 
On Fri, Sep 30, 2016 at 10:47:09AM +0530, Amit Kumar wrote:
> Signed-off-by: Amit Kumar 
> 
> This is a test patch.
> Is this patch in right format?

What exactly do you mean by "right format"?  What do you want reviewed
here, the content of the patch, or the other stuff around the patch
(subject, changelog, etc.)?

thanks,

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[PATCH] INITEST: Documentation: Explains how INITEST works.

2016-09-29 Thread Amit Kumar 
Signed-off-by: Amit Kumar 

This is a test patch.
Is this patch in right format?
---
 Documentation/initest.txt | 7 +++
 1 file changed, 7 insertions(+)
 create mode 100644 Documentation/initest.txt

diff --git a/Documentation/initest.txt b/Documentation/initest.txt
new file mode 100644
index 000..eed4124
--- /dev/null
+++ b/Documentation/initest.txt
@@ -0,0 +1,7 @@
+INITEST
+
+1) This is the same user space program /sbin/init, but for the purpose of 
testing kernel system calls.
+
+2) It will also use testing drivers to test internal kernel API.
+
+3) This is a test patch.
-- 
2.7.4


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Sending Patches using official Mail id

2016-09-29 Thread Greg KH 
On Fri, Sep 30, 2016 at 12:32:16AM +0530, Raul Piper wrote:
> Hi,
> How can I send the patches to the kernel mainline  using official mail
> id using git-send?

What do you mean by "official mail id"?

> I am using microsoft exchange server and outlook as a client.What
> configuration i have to do on my linux or WIndows PC development
> machine.
> I have read about the IMAP configuration but not sure how to achieve
> it.Can someone please post the full details.
> Documentation/email-client.txt doesn't talk anything about the
> Microsoft Exchange server.

Because almost always, exchange will corrupt patches.

Send one to yourself to try first.

But if you can use exchange as an imap server, great, use git send-email
that way and see what happens (again, test on yourself first.)
Instructions for how to set that up can be found in the man pages and by
asking your mail admin for the imap details.

> Or using my gmail id would be the last resort?

That works well too.  Good luck!

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Sending Patches using official Mail id

2016-09-29 Thread Raul Piper 
On Fri, Sep 30, 2016 at 12:37 AM, Giedrius Statkevičius
 wrote:
> On Thu, Sep 29, 2016 at 10:02 PM, Raul Piper  wrote:
>> Hi,
>> How can I send the patches to the kernel mainline  using official mail
>> id using git-send?
>> I am using microsoft exchange server and outlook as a client.What
>> configuration i have to do on my linux or WIndows PC development
>> machine.
>> I have read about the IMAP configuration but not sure how to achieve
>> it.Can someone please post the full details.
>> Documentation/email-client.txt doesn't talk anything about the
>> Microsoft Exchange server.
>> Or using my gmail id would be the last resort?
>> Thanks in advance !
>> Regards,
>> Rp
>>
> (oops, replying to all now)
>
> `git send-email` is very handy. I think you should read the corresponding
> manual page. It even has nice, very relevant examples to you as a kernel
> developer.
have you tried it using a corporate email id not the gmail id?
which Exchange server you have used?You do it on windows or linux?

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Sending Patches using official Mail id

2016-09-29 Thread Raul Piper 
Hi,
How can I send the patches to the kernel mainline  using official mail
id using git-send?
I am using microsoft exchange server and outlook as a client.What
configuration i have to do on my linux or WIndows PC development
machine.
I have read about the IMAP configuration but not sure how to achieve
it.Can someone please post the full details.
Documentation/email-client.txt doesn't talk anything about the
Microsoft Exchange server.
Or using my gmail id would be the last resort?
Thanks in advance !
Regards,
Rp

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Valdis . Kletnieks 
On Thu, 29 Sep 2016 17:54:55 +0530, Madhu K said:

> Linux BLR-PCUB-01141 4.5.0-rc7
> vermagic:   4.5.0-rc7+ SMP mod_unload modversions 686

One is a straight 4.5.0-rc7 (and why are you using that and not the
released 4.5.0, anyhow?), and the other is 4.5.0-rc7+ with a plus sign,
which means you've changed the source tree (what did you do to it?)


pgpZjkXZOERzq.pgp
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Greg KH 
On Thu, Sep 29, 2016 at 05:57:47PM +0530, Madhu K wrote:
> Hi,
> 
> I am runnig 4.0.5_rc7 kernel and I built the module for same kernel.
> 
> uname -a output :
> 
> Linux BLR-PCUB-01141 4.5.0-rc7 #2 SMP Wed Mar 23 15:51:13 IST 2016 x86_64
> x86_64 x86_64 GNU/Linux

"4.5.0-rc7" is different han "4.0.5_rc7" :)

> 
> And my modinfo of my module is :
> 
> icense:    Dual BSD/GPL
> srcversion: 1D16256F51E63BC3632B65B
> depends:   
> vermagic:   4.5.0-rc7+ SMP mod_unload modversions 686

That's the issue right there, the module was built for "4.5.0-rc7+" and
you are running "4.5.0-rc7".  Notice the "+" character?  That's the
problem here...

Run the same kernel version as your module and all should be fine.

Note, the "+" means that there are commits past the last tag in your
tree (or that it has been modified in some way since that tag).  So
there is a real difference here, which is why insmod is failing.

If you really think you can ignore this, you can always tell insmod to
ignore the kernel version check.  Read the man page for all of the
details there.

good luck!

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Alexander Kapshuk 
On Thu, Sep 29, 2016 at 3:24 PM, Madhu K  wrote:
> Hi,
>
> uname -a output :
>
> Linux BLR-PCUB-01141 4.5.0-rc7 #2 SMP Wed Mar 23 15:51:13 IST 2016 x86_64
> x86_64 x86_64 GNU/Linux
>
> And my modinfo of my module is :
>
> icense:Dual BSD/GPL
> srcversion: 1D16256F51E63BC3632B65B
> depends:
> vermagic:   4.5.0-rc7+ SMP mod_unload modversions 686
>
>
> So both are machining, what could be the problem?
>
> Regards,
> Madhu
>
> On Thu, Sep 29, 2016 at 5:40 PM, Johannes Thoma 
> wrote:
>>
>> Type
>>
>> uname -a
>>
>> on the box where you try the insmod. If it says anything else than
>> 4.0.5-rc7+ for the kernel version then this is the reason why insmod fails.
>>
>> Best
>>
>> Johannes
>
>
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

They do not match.

'uname -a': says 4.5.0-rc7.

Whereas your original post said: 4.0.5_rc7+.

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Madhu K 
Hi,

I am runnig 4.0.5_rc7 kernel and I built the module for same kernel.

uname -a output :

Linux BLR-PCUB-01141 4.5.0-rc7 #2 SMP Wed Mar 23 15:51:13 IST 2016 x86_64
x86_64 x86_64 GNU/Linux

And my modinfo of my module is :

icense:Dual BSD/GPL
srcversion: 1D16256F51E63BC3632B65B
depends:
vermagic:   4.5.0-rc7+ SMP mod_unload modversions 686

Regards,
Madhu

On Thu, Sep 29, 2016 at 5:44 PM, Greg KH  wrote:

> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
>
> http://daringfireball.net/2007/07/on_top
>
> On Thu, Sep 29, 2016 at 05:31:52PM +0530, Madhu K wrote:
> > No it is not the requirement, when I downloaded the source "4.0.5-rc7+"
> was
> > latest. Is there any problem with 4.0.5-rc7+?
>
> I do not understand these two sentences.
>
> You said you tried to load a module built for the 4.0.5-rc7 kernel tree
> (which is a very odd kernel version number, as I don't recall ever
> making a -rc7 for 4.0.5, which was released way back in June of 2015,
> but that's another issue...) In order to do that properly, you have to
> be running that specific kernel version at the same time so this will
> work properly.
>
> So, what specific kernel version are you currently running?  Does it
> match up with the kernel version of the module you are wanting to load?
> (exercise for exactly how to determine both of these is left for the
> reader...)
>
> thanks,
>
> greg k-h
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Madhu K 
Hi,

uname -a output :

Linux BLR-PCUB-01141 4.5.0-rc7 #2 SMP Wed Mar 23 15:51:13 IST 2016 x86_64
x86_64 x86_64 GNU/Linux

And my modinfo of my module is :

icense:Dual BSD/GPL
srcversion: 1D16256F51E63BC3632B65B
depends:
vermagic:   4.5.0-rc7+ SMP mod_unload modversions 686


So both are machining, what could be the problem?

Regards,
Madhu

On Thu, Sep 29, 2016 at 5:40 PM, Johannes Thoma 
wrote:

> Type
>
> uname -a
>
> on the box where you try the insmod. If it says anything else than
> 4.0.5-rc7+ for the kernel version then this is the reason why insmod fails.
>
> Best
>
> Johannes
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Greg KH 
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?


http://daringfireball.net/2007/07/on_top

On Thu, Sep 29, 2016 at 05:31:52PM +0530, Madhu K wrote:
> No it is not the requirement, when I downloaded the source "4.0.5-rc7+" was
> latest. Is there any problem with 4.0.5-rc7+?

I do not understand these two sentences.

You said you tried to load a module built for the 4.0.5-rc7 kernel tree
(which is a very odd kernel version number, as I don't recall ever
making a -rc7 for 4.0.5, which was released way back in June of 2015,
but that's another issue...) In order to do that properly, you have to
be running that specific kernel version at the same time so this will
work properly.

So, what specific kernel version are you currently running?  Does it
match up with the kernel version of the module you are wanting to load?
(exercise for exactly how to determine both of these is left for the
reader...)

thanks,

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

AW:insmod failing to insert a simple module

2016-09-29 Thread Johannes Thoma 
Typeuname -aon the box where you try the insmod. If it says anything else than 4.0.5-rc7+ for the kernel version then this is the reason why insmod fails.BestJohannes___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Quentin Lambert 


On 29/09/2016 14:01, Madhu K wrote:
> No it is not the requirement, when I downloaded the source 
> "4.0.5-rc7+" was latest. Is there any problem with 4.0.5-rc7+?
What Greg is telling you is that for you to be able to insmod a module 
you need to be running the same kernel version as the source code 
against which you have compiled your module.

If you are running kernel 4.0.0, you won't be able to insmod your module 
that has been compiled using the "4.0.5-rc7+" source code.

Quentin
>
> Thanks,
> Madhu
>
> On Thu, Sep 29, 2016 at 4:54 PM, Greg KH  > wrote:
>
> On Thu, Sep 29, 2016 at 03:26:49PM +0530, Madhu K wrote:
> > Hi All,
> >
> > While inserting a kernel module, insmod is failing with
> following error.
> >
> >
> > insmod: error inserting 'page_walk.ko': Invalid module format.
> >
> > I verified the modinfo of "page_walk.ko" it is showing version
> magic as : 4.0.5_rc7+ SMP mod_unload modversions 686
>
> Is the kernel version that you are currently running also 4.0.5-rc7+?
> That is a requirement :)
>
> > what does "mod_unload" mean here?
>
> You have enabled the ability to unload modules.
>
> Also look in your kernel log for any specific error messages when
> trying
> to load a module, it usually will be more verbous than the insmod
> program itself.
>
> good luck,
>
> greg k-h
>
>
>
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Madhu K 
No it is not the requirement, when I downloaded the source "4.0.5-rc7+" was
latest. Is there any problem with 4.0.5-rc7+?

Thanks,
Madhu

On Thu, Sep 29, 2016 at 4:54 PM, Greg KH  wrote:

> On Thu, Sep 29, 2016 at 03:26:49PM +0530, Madhu K wrote:
> > Hi All,
> >
> > While inserting a kernel module, insmod is failing with following error.
> >
> >
> > insmod: error inserting 'page_walk.ko': Invalid module format.
> >
> > I verified the modinfo of "page_walk.ko" it is showing version magic as
> : 4.0.5_rc7+ SMP mod_unload modversions 686
>
> Is the kernel version that you are currently running also 4.0.5-rc7+?
> That is a requirement :)
>
> > what does "mod_unload" mean here?
>
> You have enabled the ability to unload modules.
>
> Also look in your kernel log for any specific error messages when trying
> to load a module, it usually will be more verbous than the insmod
> program itself.
>
> good luck,
>
> greg k-h
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Greg KH 
On Thu, Sep 29, 2016 at 03:26:49PM +0530, Madhu K wrote:
> Hi All,
> 
> While inserting a kernel module, insmod is failing with following error.
> 
> 
> insmod: error inserting 'page_walk.ko': Invalid module format.
> 
> I verified the modinfo of "page_walk.ko" it is showing version magic as : 
> 4.0.5_rc7+ SMP mod_unload modversions 686

Is the kernel version that you are currently running also 4.0.5-rc7+?
That is a requirement :)

> what does "mod_unload" mean here?

You have enabled the ability to unload modules.

Also look in your kernel log for any specific error messages when trying
to load a module, it usually will be more verbous than the insmod
program itself.

good luck,

greg k-h

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Madhu K 
How to check correct headers, and when I download or clone the latest
kernel don't they provide the headers along with kernel ?

Thanks,
Madhu

On Thu, Sep 29, 2016 at 4:00 PM, Pasquier, Thomas 
wrote:

> Did you verify that you are building your module against the correct
> headers?
>
> On Thu, Sep 29, 2016 at 5:56 AM, Madhu K  wrote:
>
>> Hi All,
>>
>> While inserting a kernel module, insmod is failing with following error.
>>
>> insmod: error inserting 'page_walk.ko': Invalid module format.
>>
>> I verified the modinfo of "page_walk.ko" it is showing version magic as : 
>> 4.0.5_rc7+ SMP mod_unload modversions 686
>>
>> what does "mod_unload" mean here?
>>
>> Thanks,
>>
>> Madhu
>>
>>
>> ___
>> Kernelnewbies mailing list
>> Kernelnewbies@kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>
>
> --
> Thomas PASQUIER (home page )
> Postdoctoral Fellow
> Center for Research on Computation and Society
> School of Engineering and Applied Sciences (SEAS)
> Harvard University
>
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: insmod failing to insert a simple module

2016-09-29 Thread Pasquier, Thomas 
Did you verify that you are building your module against the correct
headers?

On Thu, Sep 29, 2016 at 5:56 AM, Madhu K  wrote:

> Hi All,
>
> While inserting a kernel module, insmod is failing with following error.
>
> insmod: error inserting 'page_walk.ko': Invalid module format.
>
> I verified the modinfo of "page_walk.ko" it is showing version magic as : 
> 4.0.5_rc7+ SMP mod_unload modversions 686
>
> what does "mod_unload" mean here?
>
> Thanks,
>
> Madhu
>
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>


-- 
Thomas PASQUIER (home page )
Postdoctoral Fellow
Center for Research on Computation and Society
School of Engineering and Applied Sciences (SEAS)
Harvard University
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

insmod failing to insert a simple module

2016-09-29 Thread Madhu K 
Hi All,

While inserting a kernel module, insmod is failing with following error.

insmod: error inserting 'page_walk.ko': Invalid module format.

I verified the modinfo of "page_walk.ko" it is showing version magic
as : 4.0.5_rc7+ SMP mod_unload modversions 686

what does "mod_unload" mean here?

Thanks,

Madhu
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: Virtual Address Space

2016-09-29 Thread arshad hussain 

> On 28-Sep-2016, at 10:36 am, Madhu K  wrote:
> 
> Hi All,

The support comes right through from the architecture. 

Linear address: Also virtual address. This is Address CPU can address. This is 
0 - 4GB under 32bit architecture.
Physical address: This are actual memory installed in your system. Linear 
address have to be converted to 
physical address eventually. MMU translate linear address with the help of 
paging to physical address.


> 
> This is to understand the Virtual address space.Basically who generates the 
> virtual addresses CPU or GNU compiler?

A program image generated by compiler & linker uses Virtual Address . During 
execution of the program CPU + MMU 
translates or maps each virtual address to physical address.

Net-net this is architecture dependent and would highly recommend reading 
Intel’s Architecture Manual for your reference.

> 
> Thanks
> Madhu
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

My recent spam on the lists.

2016-09-29 Thread Raymond Jennings 
I don't know why but claws decided to crap itself and spam everyone with
half-typed versions of the same message.  My internet was flaking out at
the time too.

Anyone know what happened, and any ideas for a more stable client that
doesn't half-ass a message in multiple spammy chunks?

Also, is it anything to do with gmail's SMTP?
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies