What could be reasons for the following message:
BUG: spinlock lockup suspected on CPU#0, sh/11786
lock: kmap_lock+0x0/0x40, .magic: dead4ead, .owner: sh/11787, .owner_cpu: 1
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.k
Enable this CONFIG_CC_STACKPROTECTOR and you will get crash.
Stack overflow does'nt necessarily creates kernel panic ;)
On Thu, Sep 13, 2012 at 5:00 PM, Denis Kirjanov wrote:
> At the moment of forking a new process do_fork() creates a new stack for the
> task by using alloc_thread_info_node():
>
k with same disk block size ?
>
>
> On Sat, Aug 6, 2011 at 9:51 PM, mani wrote:
>
>> Dear Ashish,
>>
>> The ls uses st_size while du uses st_blocks.
>> try using the ls -ls it will give you both the o/p's .
>>
>> Thanks
>> Manish
>>
&g
> You may even need to hole punch after the writes. Both xfs and ext4
> support both fallocate and hole punching. (I don't know the userspace call
> to hole punch. I think its a relatively new feature for ext4.)
> >
> > Greg
> >
> > On Aug 4, 2011 10:1
I write 1 program to create sparse file which contains alternate empty
blocks and data blocks. For example block1=empty, block2=data, block3=empty
.
#define BLOCK_SIZE 4096
void *buf;
int main(int argc, char **argv)
{
buf=malloc(512);
memset(buf,"a",512);
int fd=0;
int i;
int sector_per_block=
