linux-kernel - Re: [PATCH] exec: Make do_coredump more robust and safer when using pipes in core

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: <m1k52wrps0.fsf@fess.ebiederm.org>
Date:	Sun, 28 Jun 2009 14:50:55 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Neil Horman <nhorman@...driver.com>,
	linux-kernel@...r.kernel.org, earl_chew@...lent.com,
	Oleg Nesterov <oleg@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] exec: Make do_coredump more robust and safer when using pipes in core_pattern

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Sun, 28 Jun 2009 23:00:54 +0200 Andi Kleen <andi@...stfloor.org> wrote:
>
>> > 
>> > When was the last time we saw a "warning: process `%s' used the
>> > obsolete bdflush system call" warning?  A quick google here says 2004. 
>> > Is that data?  A bit, I guess.
>> 
>> bdflush? 
>
> I don't understand your answer.
>
> Many years ago (guess: 2001/2002) the bdflush() syscall was deprecated
> and we did
>
> 	if (msg_count < 5) {
> 		msg_count++;
> 		printk(KERN_INFO
> 			"warning: process `%s' used the obsolete bdflush"
> 			" system call\n", current->comm);
> 		printk(KERN_INFO "Fix your initscripts?\n");
> 	}
>
> to encourage people to stop using it.  A brief search indicates that
> nobody has reported this message in 4-5 years.
>
> So to answer the question "how long must we leave things in place before
> removing them?", that's the only data I am aware of.

Good point.  I just did a quick search and I can find people hitting the
deprecated sysctl message in 2.6.30.  So next year might be too soon
to actually remove the code.  Still we can remove the internal APIs
for 2.6.32 so it is no big deal.

Eric

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