* [PATCH] copy_process: cosmetic ->ioprio tweak
@ 2006-08-20 14:53 Oleg Nesterov
2006-08-21 21:32 ` Andrew Morton
0 siblings, 1 reply; 3+ messages in thread
From: Oleg Nesterov @ 2006-08-20 14:53 UTC (permalink / raw)
To: Jens Axboe; +Cc: Andrew Morton, linux-kernel
copy_process:
// holds tasklist_lock + ->siglock
/*
* inherit ioprio
*/
p->ioprio = current->ioprio;
Why? ->ioprio was already copied in dup_task_struct(). I guess this is needed
to ensure that the child can't escape sys_ioprio_set(IOPRIO_WHO_{PGRP,USER}),
yes?
In that case we don't need ->siglock held, and the comment should be updated.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
--- 2.6.18-rc4/kernel/fork.c~1_fork 2006-08-19 17:50:56.000000000 +0400
+++ 2.6.18-rc4/kernel/fork.c 2006-08-20 18:18:47.000000000 +0400
@@ -1138,7 +1138,6 @@ static struct task_struct *copy_process(
/* Our parent execution domain becomes current domain
These must match for thread signalling to apply */
-
p->parent_exec_id = p->self_exec_id;
/* ok, now we should be set up.. */
@@ -1161,6 +1160,9 @@ static struct task_struct *copy_process(
/* Need tasklist lock for parent etc handling! */
write_lock_irq(&tasklist_lock);
+ /* for sys_ioprio_set(IOPRIO_WHO_PGRP) */
+ p->ioprio = current->ioprio;
+
/*
* The task hasn't been attached yet, so its cpus_allowed mask will
* not be changed, nor will its assigned CPU.
@@ -1220,11 +1222,6 @@ static struct task_struct *copy_process(
}
}
- /*
- * inherit ioprio
- */
- p->ioprio = current->ioprio;
-
if (likely(p->pid)) {
add_parent(p);
if (unlikely(p->ptrace & PT_PTRACED))
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] copy_process: cosmetic ->ioprio tweak
2006-08-20 14:53 [PATCH] copy_process: cosmetic ->ioprio tweak Oleg Nesterov
@ 2006-08-21 21:32 ` Andrew Morton
2006-08-22 18:27 ` Oleg Nesterov
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Morton @ 2006-08-21 21:32 UTC (permalink / raw)
To: Oleg Nesterov; +Cc: Jens Axboe, linux-kernel
On Sun, 20 Aug 2006 18:53:21 +0400
Oleg Nesterov <oleg@tv-sign.ru> wrote:
> copy_process:
> // holds tasklist_lock + ->siglock
> /*
> * inherit ioprio
> */
> p->ioprio = current->ioprio;
>
> Why? ->ioprio was already copied in dup_task_struct().
It might just be a thinko.
> I guess this is needed
> to ensure that the child can't escape sys_ioprio_set(IOPRIO_WHO_{PGRP,USER}),
> yes?
How could the child escape that if this assignment was not present?
> In that case we don't need ->siglock held, and the comment should be updated.
Surely.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] copy_process: cosmetic ->ioprio tweak
2006-08-21 21:32 ` Andrew Morton
@ 2006-08-22 18:27 ` Oleg Nesterov
0 siblings, 0 replies; 3+ messages in thread
From: Oleg Nesterov @ 2006-08-22 18:27 UTC (permalink / raw)
To: Andrew Morton; +Cc: Jens Axboe, linux-kernel
On 08/21, Andrew Morton wrote:
>
> On Sun, 20 Aug 2006 18:53:21 +0400
> Oleg Nesterov <oleg@tv-sign.ru> wrote:
>
> > copy_process:
> > // holds tasklist_lock + ->siglock
> > /*
> > * inherit ioprio
> > */
> > p->ioprio = current->ioprio;
> >
> > Why? ->ioprio was already copied in dup_task_struct().
>
> It might just be a thinko.
>
> > I guess this is needed
> > to ensure that the child can't escape sys_ioprio_set(IOPRIO_WHO_{PGRP,USER}),
> > yes?
>
> How could the child escape that if this assignment was not present?
It is possible that sys_ioprio_set(IOPRIO_WHO_PGRP) was called after
copy_process() already did dup_task_struct(), but before it takes
tasklist_lock. Documentation/block/ioprio.txt doesn't say should
ioprio_set() be "atomic" or not. If not, we can kill this line, and
(more importantly) drop tasklist_lock in fs/ioprio.c
Oleg.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-08-22 14:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-20 14:53 [PATCH] copy_process: cosmetic ->ioprio tweak Oleg Nesterov
2006-08-21 21:32 ` Andrew Morton
2006-08-22 18:27 ` Oleg Nesterov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox