linux-kernel - Re: [0/7] Distributed storage for drivers/staging merge request

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <496DB2EF.70405@garzik.org>
Date:	Wed, 14 Jan 2009 04:39:59 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Evgeniy Polyakov <zbr@...emap.net>
CC:	greg@...ah.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, dst@...emap.net
Subject: Re: [0/7] Distributed storage for drivers/staging merge request

Andrew Morton wrote:
> On Wed, 14 Jan 2009 03:20:08 +0300
> Evgeniy Polyakov <zbr@...emap.net> wrote:
> 
>> And while you at it, please shed a
>> light on this exports for POHMELFS:
>>
>> --- a/mm/filemap.c
>> +++ b/mm/filemap.c
>> @@ -513,6 +513,7 @@ int add_to_page_cache_lru(struct page *page, struct address_space *mapping,
>>  	}
>>  	return ret;
>>  }
>> +EXPORT_SYMBOL_GPL(add_to_page_cache_lru);
> 
> OK by me.
> 
>>  #ifdef CONFIG_NUMA
>>  struct page *__page_cache_alloc(gfp_t gfp)
>> @@ -627,6 +628,7 @@ int __lock_page_killable(struct page *page)
>>  	return __wait_on_bit_lock(page_waitqueue(page), &wait,
>>  					sync_page_killable, TASK_KILLABLE);
>>  }
>> +EXPORT_SYMBOL_GPL(__lock_page_killable);
> 
> Needed for modular use of lock_page_killable() - makes sense.
> 
> Please maintain these alongside the pohmelfs patchset.

FWIW we definitely want pohmelfs in staging...

(yes, I realize we are discussing dst not pohmelfs)

	Jeff




--
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/