GATE CSE 2005 | Question: 72

Question

Consider the following code fragment:
if (fork() == 0)
{
   a = a + 5;
   printf("%d, %p n", a, &a);
}
else
{
   a = a - 5;
   printf ("%d, %p n", a,& a);
}

Let $u,v$ be the values printed by the parent process and $x,y$ be the values printed by the child process. Which one of the following is TRUE?

• A. $u = x + 10  \text{ and } v = y$
• B. $u = x + 10 \text{ and } v != y$
• C. $u + 10 = x \text{ and } v = y$
• D. $u + 10 = x \text{ and } v != y$

Comments

yeh parent and child don't have some address.

---

After fork(), the parent and child processes initially share the same physical memory pages using the copy-on-write mechanism. When either process attempts to modify a shared page, the operating system creates a separate physical copy of that page for the modifying process. However, both processes continue to use the same virtual (logical) addresses for their variables. Therefore, although the parent and child have different physical memory after a write, the virtual address of a variable (as printed by &a in printf) remains the same in both processes, because user programs only see virtual addresses, not physical addresses.

---

This is how Address Remains the same 

Answer 1

It should be Option C.

#include<stdio.h>
#include<stdlib.h>
void main()
{
    int a =100;
    if(fork()==0)
    {
     a=a+5;
     printf("%d %d \n",a,&a );
    }
   else
    {
     a=a-5;
     printf("%d %d \n",a,&a );
    }
}

Output:

Fork returns $0$ when it is a child process.

if ( fork == 0)              

Is true when it is child . Child increment valule of a .

In the above output:

• $95$ is printed by parent : $\mathbf{u}$
• $105$ is printed by child  : $\mathbf{x}$
  $\mathbf{\Rightarrow u+10=x}$

The logical addresses remains the same between the parent and child processes.

Hence, answer should be:

 $\mathbf{ u+10=x}$  and $\mathbf{v=y}$

Comments

Just write 'child' and 'parent' before printing the values. It will make it clear

---

@pc @sudarshana.

Lets consider single level paging system. Now, if virtual addresses are same means offset in the page table is same. So, from the output shown above, how can Page table entry(PTE) be different for child and parent?

---

@Sushant

Virtual adress of 'a' will be same for child unless execv() is called immediately after fork for child. When a parent forks, the child will get the same VA space as the parent, but all the page table entries are marked read-only. When either child/parent tries modifying the page, a page fault will ensue (copy-on-write) and the OS pages in a new page, copy the old contents and mark the the page as RW for both parent and child. Now, the PTE will be different for both parent and child. (But virtual address is still the same)

Please correct me if I am wrong.

---

@Sudarshana. You agree copy-on-write is required here. So, physical pages for child and parent are different.  Now, question is are they accessing the same location in page table ? Now, as you said PTE's will be different. SO, what will happen if parent and child access the same location in page table at the same time?

Could you draw a diagram as to how the virtual addresses can be same for 2 processed(either 1 level paging or multi-level paging)?

---

SO, what will happen if parent and child access the same location in page table at the same time?

We have 2 process here-child and parent and both will have separate page tables. 

I found this explaination SO: It may help: 

Lets say your process is got var name X that have a virtual address 100 and physical address 200. the PTE is holding a mapping of addresses from virtual 100 to physical 200. After the fork, each process (parent and child) will have his private PTE. at this point both PTEs will map virtual 100 to physical 200. as long as both process just read from there they both will read from physical address 200. When the first one will try to write there, the data from physical address will be copy to a new physical space, lets say 300, and his (and only his) PTE will be update so virtual 100 will be mapped to physical 300. that way it's transparent to the process because he is still using the same (virtual) address.                 *Note: this is just an abstract, and the real thing is happening in page resolution.

Link of SO: http://stackoverflow.com/a/6200398 

---

@suarshana. Great :) thanks for the help.

---

this is superb

---

Awesome question. Good doubt @ Sushant Gokhale  and nicely answered :)

---

you dont have any work other than downvoting...ab ise bhi karo downvote.

---

hey, the address printed should be physical address ,no?

and physical address is different for both child process and parent process.

can you provide me the reason as to why u r considering logical address?

---

@sachi, physical addresses are transparent to the process (it means processes are not aware of their physical addresses).They can only see their virtual address..so. the program will print virtual address which are always same for both parent and child process.

---

Every process will hav its own PCB .... So here the values of child will not affect the values of parent ... Bt the addresses will be same as fork copies data from parent and creates child process ...

---

they didn't mentioned about it is logical address yet.in question.we should consider it as physical or logical.

if physical address of parent is stored in v

if physical address of child is stored in y

then v!=y.explain me where i am wrong.

---

v!=y is true... Answer must be option D

---

NOT GETTING V=Y CONCEPT ????

---

@pC please explain how V=Y is true

---

V and Y are the logical/addresses that maps to different physical location[differnet copies of a here] after if either parent/child writes ..so these are same logical addresses , mapping to different physical page ..hence v = y ..

---

@jatin

your logic seems to be correct for me

---

why not  v!=y???

---

Both variables can never be at same location v can never be equal to y.

---

I also got same result 👍

Answer 2

answer is c because when child is created, it gets a saparate address space i.e. space in RAM and it clones entire address space of parent into it's own address space. so obviously the variable 'a' is also copied and physical address i.e. location in RAM would be different for both variables. but given program doesn't print the physical address, it prints the logical address i.e. distance between the location of variable in RAM and location of start of address space for the process i.e. relative location of variable with respect to start of it's address space which will be same for both parent and child since data is cloned.

 

in unix tho, address space of parent and child is also same until one of them tries to modify the contents of it's address space. then they are assigned different address spaces and cloning is done.

now before you go on to solve next question, you deserve to see this bunny with a backpack--

Comments

@MiNiPanda Because OS doesn't allow it, process is not aware of it. It is impossible to access physical address without working in a kernel mode (and we don't work on kernel mode on OS). Also, printf() always prints logical address, which is same for both the processess.

It's like you have two completely same books( process), every page in the book has same letters at same page no.(same address of same variable), but they are actually different books (different process) stored in different locations.

---

That bunny is so cuteee !! 😍

---

great explanation

Answer 3

(c) is the answer. Child is incrementing a by 5 and parent is decrementing a by 5. So, x = u + 10.

During fork(), address space of parent is copied for the child. So, any modifications to child variable won't affect the parent variable or vice-verse. But this copy is for physical pages of memory. The logical addresses remains the same between the parent and child processes.

Comments

@avinash Here &a means logical address bcoz of security matter ...

---

it should be option C ?

---

Wrong because child and parent are stored in separate memory locations. V can't be equal to Y.

Answer 4

fork() returns 0 in child process and process ID of child process in parent process.
In Child (x), a = a + 5
In Parent (u), a = a – 5;

Child process will execute the if part and parent process will execute the else part. Assume that the initial value of a = 6. Then the value of a printed by the child process will be 11, and the value of a printed by the parent process in 1. Therefore u+10=x.

the virtual address is same but virtual addresses exist in different processes’ virtual address space and when we print &a, it’s actually printing the virtual address. Hence the answer is v = y.

Answer 5

Option C....

In the question, the child and parent processes are as follows :

Child =>  a = a + 5, 
                printf("%d, %p n", a, &a);

Values are gives as x = a, and y = &a

Parent => a = a - 5
                 printf("%d, %p n", a, &a);

Values are gives as u = a, and v = &a

Now, &a prints Logical address, and during fork() we create an exact same copy of the process and the variables are stored at the same logical address, while at different physical addresses.

So that's why, y=v, 

Now as written above, physical address is different, so x and u are different, x = a + 5, u = a - 5, Now we can easily find relation b/w x and u, which is x = u + 10.

Answer 6

$u, v$ values printed by the parent process.
$u=a-5; v$ be address of $a$
$a=u+5;$
$x, y$ values printed by the child process.
$x=a+5; y$ be the address of $a$
$x=u+5+5; v=y$
$x=u+10$