Re: Work with correct branch for kernel changes

[Andrey Skvortsov]

On 12 Dec, Shirish Gajera wrote:
> Hi,
> 
> I am new to linux kernel and trying to understand  the process of
> different git branch to work.
> 
> So, if I am not wrong then there are different branch like stable, next,
> staging etc. Previously I work with staging branch so if I am making
> any changes for drivers/staging I have to work with staging branch like
> follow.
> git clone 
> git checkout -t -b staging-testing origin/staging-testing
> git chekcout -b MY_LOCAL_BRANCH
> not do work and subimt
> 
> So, how it work for other source structure, like now I want to make some
> for y2038 -> drivers/scsi which branch should I set up and work with,
> next/stable/or is there any specific y2038 branch.
> 
> Any wiki link or documentation that explain this full process which
> branch to work with when making changes to specific directory will be
> useful.
> 
> Thanks,
> Shirish

There are not only different branches, but also different git trees,
where development for different subsystem takes place usually.

I recommend you to watch this presentation of GregKH. He explains very
good, how the development is working.

https://kernel-recipes.org/en/2014/the-linux-kernel-how-fast-it-is-developed-and-how-we-stay-sane-doing-it/

-- 
Best regards,
Andrey Skvortsov

Secure eMail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD


signature.asc
Description: PGP signature
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Customizing UIO mmap'ing

[Kenneth Adam Miller]

So, previously I think I misunderstood how to use uio_dmem_genirq. Let me
explain the way I think it currently works (bare with me, I departed from
looking at this driver after only about a week of looking at it):

Generally uio_dmem_genirq.c builds on top of uio.c, which provides a common
module basis for isolating code common to the other specific modules. But
for a specific purpose, uio_dmem_genirq.c has be either customized or
extended in order that specific memory regions can be set as accessible.
Most easily, this is done in a first come first serve approach by filling
out the details (which exactly?) left missing in uio_dmem_genirq.c, and to
start, that would be in uio_of_genirq_match

.

Am I correct?
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Track execution of close() system call in kernel

[Harsh Jain]

Hi,

How to track the code flow of close() system call for socket fds.

In working case I am getting following debug traces in dmesg

inet_release sk 88040e376000 sk->sk_prot->close a0774a50
chelsio_close Entered
CPU: 3 PID: 10108 Comm: openssl Tainted: G   O
3.17.8_harsh_cry_test_dis #28
Hardware name: Supermicro X8ST3/X8ST3, BIOS 2.007/29/10
  8800d87ebde8 815e8356 81dc21a0
 88040e376000 8800d87ebe28 a0774a91 88040646f880
 88040e376000  8803fef299c0 8803fef299f0
Call Trace:
 [] dump_stack+0x51/0x6b
 [] chelsio_close+0x41/0x340 [t4_tom]
 [] inet_release+0xc0/0xd0
 [] sock_release+0x29/0xa0
 [] sock_close+0x12/0x20
 [] __fput+0xd0/0x260
 [] fput+0xe/0x10
 [] task_work_run+0xad/0xe0
 [] do_notify_resume+0x84/0x90
 [] int_signal+0x12/0x17
chelsio_close Exit


After doing changes in kernel module dumpstack is not getting printed
from "chelsio_close" function. I added function entry/exit trace in
"sock_release" also. Return value of close() system call is also zero.
Its executing successfully but where in kernel code?



Regards
Harsh Jain

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