Hi Darshan,
Replying to all this time
On Thu, Jan 19, 2012 at 9:41 PM, Darshan Ghumare
wrote:
...snip...
> What if,
> spin_lock_irqsave(&lock, flags);
> for ( ; ; )
> {
> ;
> }
> spin_lock_irqrestore(&lock, flags);
Since you're using spinlocks and disabling interrupts, this would be
Hi,
$ readelf -n core
Notes at offset 0x0274 with length 0x04c0:
OwnerData size Description
CORE 0x0090 NT_PRSTATUS (prstatus structure)
CORE 0x007c NT_PRPSINFO (prpsinfo structure)
CORE 0x00a0 NT_AUXV (a
Yes you are right.
Each architecture implements clear_page() differently. Some may just use
memset. Some may use architecture specific instructions to perform the
zero-ing faster.
I guess x86's fast_clear_page does that.
-Fredrick
On 01/18/2012 05:27 PM, 夏业添 wrote:
> Thanks!
>
> It seems that
On Thu, Jan 19, 2012 at 10:54 PM, Dave Hylands wrote:
> Hi,
> On Thu, Jan 19, 2012 at 7:26 AM, Mulyadi Santosa
> wrote:
> > Hi again :)
> >
> > On Thu, Jan 19, 2012 at 16:03, Darshan Ghumare
> > wrote:
> >> What if, there is one process which is in middle of a syscall which has
> >> infinite lo
Hi Graeme :)
On Fri, Jan 20, 2012 at 09:20, Graeme Russ wrote:
> This may not be the best place to post this question, so please excuse...
>
> I have a brand new Intel i5 / z68 EUFI motherboard (ASRock Z68 Pro3
> Gen3) with 8GB RAM running Fedora 16 (64 bit) which is experiencing
> lockups which
This may not be the best place to post this question, so please excuse...
I have a brand new Intel i5 / z68 EUFI motherboard (ASRock Z68 Pro3
Gen3) with 8GB RAM running Fedora 16 (64 bit) which is experiencing
lockups which send the video crazy (flashing screen) but there is
nothing appearing in /
On 01/11/2012 01:44 PM, Greg Freemyer wrote:
> When a linux process dies, it first becomes a zombie and the parent process
> is signaled.
>
> The parent process at that point can still do various things. If the parent
> is a debugger, it can get all sorts of details from the zombie.
>
> When th
Hi All,
Man page of waitpid give expansion with example on how to send SIGSTOP,
SIGCONT and SIGKILL/SIGTERM to a running process. If we don't implement waitpid
system call we will not be able to observer the states of process when we issue
a signal to running process.
-Anand Moon
Hi,
On Thu, Jan 19, 2012 at 7:26 AM, Mulyadi Santosa
wrote:
> Hi again :)
>
> On Thu, Jan 19, 2012 at 16:03, Darshan Ghumare
> wrote:
>> What if, there is one process which is in middle of a syscall which has
>> infinite loop in it received SIGKILL & there are no other processes in the
>> system?
On Thu, Jan 19, 2012 at 05:36:07PM +0530, sumeet linux wrote:
> Hi All,
>
> Can anyone clarify that when should I use _GPL and when not ?
> Is there a policy like for new code, it must be _GPL ?
> I see in kernel many places _GPL used like EXPORT_SYMBOL_GPL( ), but many
> places only EXPORT_SYMBOL
Hi again :)
On Thu, Jan 19, 2012 at 16:03, Darshan Ghumare
wrote:
> What if, there is one process which is in middle of a syscall which has
> infinite loop in it received SIGKILL & there are no other processes in the
> system?
infinite loop such as "for(;;)" ? well as long as it doesn't disable
On Mon, Jan 16, 2012 at 18:45, Jonathan Neuschäfer wrote:
> On Mon, Jan 16, 2012 at 01:19:22PM -0500, Scott Lovenberg wrote:
> > Let me walk you guys through how this bug could be exploited.
> > The file that you want to access is blocked from you by file system
> > permissions. The root user (ui
On Tue, Jan 17, 2012 at 20:53, Fredrick wrote:
> When you malloc a memory or mmap a MAP_ANON memory, it is virtually
> allocated. When you read or write to it, the process takes a page fault.
> The page fault handler zeroes those memory and hands it to the process.
> So I think there is no leak.
Hi All,
Can anyone clarify that when should I use _GPL and when not ?
Is there a policy like for new code, it must be _GPL ?
I see in kernel many places _GPL used like EXPORT_SYMBOL_GPL( ), but many
places only EXPORT_SYMBOL( ).
Regards,
Sumeet
___
Kern
Hi Mulyadi,
On Thu, Jan 19, 2012 at 2:16 PM, Mulyadi Santosa
wrote:
> Hi Darshan :)
>
> On Thu, Jan 19, 2012 at 14:03, Darshan Ghumare
> wrote:
> > Hi Mulyadi,
> >
> > How SIGKILL is handle by Kernel?
> > Does SIGKILL & SIGTSTP handled separately than the rest of the signals?
>
> I hope you don'
Hi Darshan :)
On Thu, Jan 19, 2012 at 14:03, Darshan Ghumare
wrote:
> Hi Mulyadi,
>
> How SIGKILL is handle by Kernel?
> Does SIGKILL & SIGTSTP handled separately than the rest of the signals?
I hope you don't mind if I cc this answer to kernelnewbies as well.
Hopefully you will get better answe
sorry guys did not read tat properly..he is just referring to user
spaceas far malloc is concerned it basically calls *brk*() and
*sbrk() * tand
they basically end up changing the location of thelocation of program break
which is nothing but the end of the process's data segment so it has
noth
17 matches
Mail list logo