linux-kernel - Re: early_printk accessing __log

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]

Date:	Tue, 31 Jul 2007 15:59:34 +0800
From:	Bryan Wu <bryan.wu@...log.com>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Robin Getz <rgetz@...ckfin.uclinux.org>,
	linux-kernel@...r.kernel.org, Greg Ungerer <gerg@...pgear.com>,
	Russell King <rmk@....linux.org.uk>,
	Paul Mundt <lethal@...ux-sh.org>,
	Tim Bird <tim.bird@...sony.com>, bryan.wu@...log.com
Subject: Re: early_printk accessing __log_buf

On Tue, 2007-07-31 at 03:47 -0400, Mike Frysinger wrote:
> On 7/24/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > On Tue, 24 Jul 2007 16:12:56 -0400 Robin Getz wrote:
> > > On Tue 24 Jul 2007 14:12, Andrew Morton pondered:
> > > > Oh well, it sounds like we need the super-duper fast version.  Keep it
> > > > as simple as possible, please.
> > >
> > > What about:
> > >
> > > int log_buf_copy(void *dest, int idx, size_t n);
> > >
> > > starting at index idx - copy n bytes to dest, return the number of bytes
> > > copied (in case there are not n bytes in the log_buf yet).
> >
> > Sounds sensible.  I'd make it return size_t and take a char* arg though.
> > Or just use `int' - size_t is a bit of a pain and this is all kernel-internal
> > anwyay.
> 
> attached
> -mike

why use attachment? You can just paste your patch in the email.

Thanks
- Bryan Wu
-
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/