linux-kernel - Re: [PATCH 0/7] V3 of the async function call patches

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090115081006.GB1599@ucw.cz>
Date:	Thu, 15 Jan 2009 09:10:06 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/7] V3 of the async function call patches


> > My dmesg shows:
> > 
> >  [    2.264955] sd 5:0:0:0: [sdb] Write cache: enabled, read cache:
> > enabled, doesn't support DPO or FUA [    2.264958]  sdb:<6>Freeing
> > unused kernel memory: 408k freed
> > 
> > Ouch. How come that "Freeing unused kernel memory" got done in the
> > middle of the sdb partition thing?
> > 
> > There's a async_synchronize_full() there before the free_initmem(),
> > but I'm worrying that it just isn't working. Hmm? What am I missing?
> > 
> 
> ok this part looks funny but it's not really (and it's safe I think).
> 
> The async sata thing launches another async thing (the scsi partition
> scan).
> The synchronize_full() waits for the sata to complete, but doesn't wait
> for things that the sata async schedules after the wait started.
> 
> is this a problem? not right now, but it means we have a rule that if
> an async item schedules another async item, the second one cannot be
> __init. (which is ok right now.. scsi already had some of this async
> anyway).
> 
> I could make the async_full() be more strict if that makes you feel
> better, but for this specific purpose it would be over-synchronizing.

Really? If you run userspace before partitions are ready, its attempts
to read partitions will result in problems, right?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/