linux-kernel - Re: [patch] x86: Unneeded assignment to tsk in recent x86 change

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <18807.36883.413974.491276@harpo.it.uu.se>
Date:	Wed, 21 Jan 2009 22:13:55 +0100
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Uros Bizjak <ubizjak@...il.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>, linux-kernel@...r.kernel.org
Subject: Re: [patch] x86: Unneeded assignment to tsk in recent x86 change

Uros Bizjak writes:
 > Mikael Pettersson wrote:
 > 
 > >  > Impact: Cleanup.
 > >  > 
 > >  > Remove unneeded assignment to tsk in recent x86 change [1].
 > >  
 > >
 > >  > @@ -795,13 +794,12 @@ asmlinkage
 > >  >  void __kprobes do_page_fault(struct pt_regs *regs, unsigned long error_code)
 > >  >  {
 > >  >  	unsigned long address;
 > >  > -	struct task_struct *tsk;
 > >  > +	struct task_struct *tsk = current;
 > >  >  	struct mm_struct *mm;
 > >  >  	struct vm_area_struct *vma;
 > >  >  	int write;
 > >  >  	int fault;
 > >  >  
 > >  > -	tsk = current;
 > >  >  	mm = tsk->mm;
 > >  >  	prefetchw(&mm->mmap_sem);
 > >
 > > but this is neither a fix nor IMO a cleanup (it's inconsistent with
 > > the other variables in that function)
 > >   
 > 
 > Hm, I'm not sure I see the inconsistency here. Care to explain this 
 > inconsistency in a couple of words?

You're initialising some variables in their declarations, and some
using assignments at the start of the procedure body. In particular,
for some reason you don't initialise 'mm' in its declaration even
though you could do so for consistency with 'tsk'.

However, I'm strongly in favour of separating declarations and
initialisations (esp. ones that need actual computations), so
rather than subjecting 'mm' to the treatment you gave 'tsk',
just leave the code alone.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/