Anton Altaparmakov <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-09-09 at 15:02 +0300, Pekka J Enberg wrote:
> > On Fri, 9 Sep 2005, Anton Altaparmakov wrote:
> > > > I completely disagree with you given that this is not "inventing
> > > > [...] own memory allocators", it is just a convenient short ha
Willy Tarreau <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 05, 2005 at 12:47:03AM -0400, Sean wrote:
[...]
> > But the real crux of the argument here is not whether or not people should
> > ever use binary-only drivers, it's whether the open source kernel
> > developers should spend any time worrying
Bas Westerbaan <[EMAIL PROTECTED]> wrote:
> > Yes you are. You're asking for 4KSTACKS config option to maintained
> > and it is not something you get for free. Besides, if it is indeed
> > ripped out of mainline kernel, you can always keep it a separate patch
> > for ndiswrapper.
> Though 4K stack
Andreas Hartmann <[EMAIL PROTECTED]> wrote:
1> Alex Riesen wrote:
> > On 9/3/05, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
> >> Hello!
> >> Is it possible to prevent a program to be straced on x86?
> >> What do I have to do, eg., to prevent a perl-program to be straced?
Look at the contortions s
Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 9/4/05, Harald Welte <[EMAIL PROTECTED]> wrote:
> > On Sun, Sep 04, 2005 at 12:12:18PM +0200, Harald Welte wrote:
> > > Hi!
> > >
> > > Below you can find a driver for the Omnikey CardMan 4040 PCMCIA
> > > Smartcard Reader.
> >
> > Sorry, the patch was m
Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On Wednesday 24 August 2005 22:39, Brian Gerst wrote:
> >
> > Do this instead:
> > char ln[LINE_SIZE], *line;
> >
> Right, now why didn't I think of that :)
>
> Jeff: Does the patch below agree with you more?
>
>
> Signed-off-by: Jesper Juhl <[EMAIL
[EMAIL PROTECTED] wrote:
>>On Thu, Aug 25, 2005 at 12:35:22AM -0400, [EMAIL PROTECTED] wrote:
>>I don't know, because tar is probably more widely used and
>>consequently people are more familiar with how to use it.
>>>As I said before, the cpio format is cleaner/easier to parse in t
Jesper Juhl <[EMAIL PROTECTED]> wrote:
> Convert strtok() use to strsep() in usr/gen_init_cpio.c
This is userland code...
No, I'm not looking it over carfully, just a fast look over.
> I've compile tested this patch and it compiles fine.
You should be able ti test it then.
> I build a 2.6.13-r
Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-08-19 at 00:10 -0700, Andrew Morton wrote:
> > Rusty Russell <[EMAIL PROTECTED]> wrote:
> > > I believe we just ignored sparc64. That usually works for solving these
> > > kind of bugs. 8)
> >
> > heh. iirc, it was demonstrable on x86 also.
Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 17, 2005 at 11:54:23AM +0200, Christian Ehrhardt wrote:
> > Your Patch at (URL wrapped)
> >
> > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git; \
> > a=commit;h=99c6e60afff8a7bc6121aeb847dab27c556cf0c9
> >
>
DervishD <[EMAIL PROTECTED]> wrote:
> * Pete Zaitcev <[EMAIL PROTECTED]> dixit:
> > On Wed, 10 Aug 2005 21:22:43 +0200, DervishD <[EMAIL PROTECTED]> wrote:
> > > I'm not using hotplug currently so... how can I make the USB
> > > subsystem to assign always the same /dev/sd? entry to my USB Mass
Xin Zhao <[EMAIL PROTECTED]> wrote:
> I want to lock down a directory to be read-only, say, /etc, for system
> security.
If root can bypass that somehow, it is useless anyway.
> Unfortunately, some valid system tools might need to
> create/modified files like "/etc/dhclient-eth0.conf".
Horst von Brand <[EMAIL PROTECTED]> wrote:
> In arch/i386/kernel/cpu/mtrr/main.c at line 225 it references
> ipi_handler(), a function that is only declared under CONFIG_SMP (from line
> 139 onwards). As a result, the build fails.
Sorry for the noise, a few minutes later the upda
In arch/i386/kernel/cpu/mtrr/main.c at line 225 it references
ipi_handler(), a function that is only declared under CONFIG_SMP (from line
139 onwards). As a result, the build fails.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> "extern inline" doesn't make much sense.
The gcc info here (4.0.1-4 on Fedora rawhide) says it means that the
function should be inlined, and no local copy should be generated
ever. This way the build will bomb out when something isn't inlined.
It also say
[EMAIL PROTECTED] wrote:
> I am currently using Slackware 10.1 with 2.4.29 kernel and encountered
> following problem:
> I use Sagem Fast 800 ADSL modem of my provider and use my linux station
> as a router (iptables+masquerade). The problem is that after a few hours
> of working my linux crashes
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Jiri Slaby napsal(a):
> > Are these files obsolete and could be deleted from tree.
> > Does anybody use them? Could anybody compile them?
>
> New list should be:
[...]
> sound/oss/skeleton.c
I think skeleton.* files are there as examples, not for real use
Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 7/11/05, Michael S. Tsirkin <[EMAIL PROTECTED]> wrote:
> [snip]
> > 3e. sizeof
> > space after the operator
> > sizeof a
> I don't think that's a hard rule, there's plenty of code that does
> "sizeof(type)" and not "sizeof (type)", a
Etienne Lorrain <[EMAIL PROTECTED]> wrote:
> > I'd like to have a discussion about FAT robustness.
> > Please give your thought, comments and related issues.
> What I would like is to treat completely differently writing to
> FAT (writing to a removeable drive) which need a complete "mount",
>
I'm getting:
# modprobe toshiba_acpi
FATAL: Error inserting toshiba_acpi
(/lib/modules/2.6.13-rc3/kernel/drivers/acpi/toshiba_acpi.ko): No such device
This is definitely a Toshiba M30 notebook with this.
On bootup I see:
ACPI: RSDP (v000 TOSHIB) @ 0x000f7a10
ACPI
Nicholas Hans Simmonds <[EMAIL PROTECTED]> wrote:
[...]
> Other than this, what are the general thoughts about this method as
> opposed to just using a well defined byte order?
I'd prefer a defined byte order. That way it won't bite too hard if I
happen to move a filesystem (image) from PC to SP
Jesse Brandeburg <[EMAIL PROTECTED]> wrote:
> On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote:
> > symptom
> > ===
> > modprobe e100
> > ifconfig eth0 netmask
> >
> > result:
> > ===
> > SIOCADDRT: Network is unreachable
> >
> > There were no such error in 2.6.13-rc2
> odd, b
Greg KH <[EMAIL PROTECTED]> wrote:
> -stable review patch. If anyone has any objections, please let us know.
> Signed-off-by: Zou Nan hai <[EMAIL PROTECTED]>
> Signed-off-by: Suresh Siddha <[EMAIL PROTECTED]>
> Cc: Andi Kleen <[EMAIL PROTECTED]>
Huh? Cc: in here?
> Signed-off-by: Andrew Morton <
Nicholas Hans Simmonds <[EMAIL PROTECTED]> wrote:
> Sorry, my earlier reply seems to have gotten lost somewhere. I've been
> pondering this issue for some time and am still not sure what's the best
> answer. I've attached a small patch which handles this by detecting byte
> swapping of the version
David Masover <[EMAIL PROTECTED]> wrote:
> Hans Reiser wrote:
> > Horst von Brand wrote:
> >>Hans Reiser <[EMAIL PROTECTED]> wrote:
> >>>Stefan Smietanowski wrote:
[...]
> > Better to spend one's mind looking for bugs instead of this issu
DervishD <[EMAIL PROTECTED]> wrote:
[...]
> It's a good idea to have a copy of the partition table around, if
> it is not simple (the one you had is NOT simple).
Be careful. What you'll get out of backing up the partition table is /only/
the primary partitions, the others are handled by a we
David Masover <[EMAIL PROTECTED]> wrote:
[...]
> Both camps seem to want to allow easy access to the metadata of a
> file, whether we're given that file as an inode or as a pathname.
> That's why I suggested /meta/vfs and /meta/inode -- sometimes I want
> to look up a file by name, and sometimes
Hans Reiser <[EMAIL PROTECTED]> wrote:
> Stefan Smietanowski wrote:
> > I think "..." and ".meta" both serve as a logical delimiter. However
> > some programs implement their own "..." which would make it clash with
> > them. Naturally if some program created a directory called .meta we're
> > equa
Marc Aurele La France <[EMAIL PROTECTED]> wrote:
> It has been more than a week now...
> -- Forwarded message --
> Date: Sun, 3 Jul 2005 11:12:03 -0600 (MDT)
> From: Marc Aurele La France <[EMAIL PROTECTED]>
> To: Linus Torvalds
> Subject: Kernel header policy
[]
> I am conta
Erik Hensema <[EMAIL PROTECTED]> wrote:
> Horst von Brand ([EMAIL PROTECTED]):
> [on reiserfs4]
> >> >> and _can_ do things
> >> >> no other FS can
> > Mostly useless things...
> Depends on yo
Roman Zippel <[EMAIL PROTECTED]> wrote:
> On Sun, 10 Jul 2005, Pekka Enberg wrote:
[...]
> > Would you please be so kind to define your criteria for things that
> > "need fixing" so we could see if can reach some sort of an agreement on
> > this. My list is roughly as follows:
> >
> > - Errone
Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 10, 2005 at 09:21:42PM +0300, Pekka Enberg wrote:
> > Hmm. So we disagree on that issue as well. I think the point of review
> > is to improve code and help others conform with the existing coding
> > style which is why I find it strange that
Ed Cogburn <[EMAIL PROTECTED]> wrote:
> David Lang wrote:
> > On Fri, 8 Jul 2005, Ed Tomlinson wrote:
> >> No Flame from me. One thing to remember is that Hans and friends
> >> _have_ supported R3 for years.
They let it fall into disrepair when they started work on 4.
> >>
Hans Reiser <[EMAIL PROTECTED]> wrote:
[...]
> I think the exokernel approach by Frans is a very interesting approach.
> I wish I had the experience with it necessary to know if it was
> effective. I do NOT take the position that name resolution should be in
> the kernel. I DO take the positio
Hubert Chan <[EMAIL PROTECTED]> wrote:
> On Wed, 06 Jul 2005 12:52:23 -0600, Jonathan Briggs <[EMAIL PROTECTED]> said:
> > On Tue, 2005-07-05 at 23:44 -0700, Hans Reiser wrote:
> >> Hubert Chan wrote:
> >>> And a question: is it feasible to store, for each
> >>> inode, its parent(s), instead of jus
David Masover <[EMAIL PROTECTED]> wrote:
[...]
> Just don't allow user-created hardlinks inside either metafs (/meta) or
> the magical meta directory inside files.
And what is it useful for, after its advantage was that it was /exactly/
like regular files &c, and now it is severely crippled?
--
Hubert Chan <[EMAIL PROTECTED]> wrote:
> On Fri, 01 Jul 2005 03:41:00 -0400, Chet Hosey <[EMAIL PROTECTED]> said:
> > Horst von Brand wrote:
> >> And who says that a normal user isn't allowed to annotate each and
> >> every file with its purpose or
Xin Zhao <[EMAIL PROTECTED]> wrote:
> I tried to do "insmod nfsd.ko", but always got the error message
> "insmod: error inserting 'nfsd.ko': -1 Unknown symbol in module"
Use modprobe(8), it knows about module dependencies and what to load.
--
Dr. Horst H. von Brand User #22616 c
Denis Vlasenko <[EMAIL PROTECTED]> wrote:
> > > > > NB: gcc 3.4.3 can use excessive stack in degenerate cases, so please
> > > > > include gcc version in your reports.
> > > >
> > > > But this can't occur in the kernel.
> > >
> > > It can. I saw the OOPS myself.
> > > One of the functions in cryp
David Masover <[EMAIL PROTECTED]> wrote:
> Horst von Brand wrote:
> > David Masover <[EMAIL PROTECTED]> wrote:
> >>David Weinehall wrote:
> >>>On Fri, Jul 01, 2005 at 03:08:58AM -0500, David Masover wrote:
> >>>>David Weinehall wrote:
[...
Petr Baudis <[EMAIL PROTECTED]> said:
[...]
> The way to work around that is to setup separate rsync URIs for each of
> the trees. ;-) I think I will make git-pasky (Cogito) accept also URIs
> in form
>
> rsync://host/path!branchname
>
> which will allow you to select the particular branc
Andreas Hartmann <[EMAIL PROTECTED]> said:
> Alacritech developed a new chip for NIC's
> (http://www.alacritech.com/html/tech_review.html), which makes it possible
> to take away the TCP stack from the host CPU. Therefore, the host CPU has
> more performance for the applications according Alacritec
"Franco \"Sensei\"" <[EMAIL PROTECTED]> said:
> David Lang wrote:
> > some config changes are additions, some redefine things.
> >
> > you are mistakeing the .config file for a symbol table.
> No I'm not confusing. As long as the .config has an influence on the
> makefiles I get different symbol
[EMAIL PROTECTED] said:
> As per http://www.nist.gov/dads/HTML/shellsort.html, this should be
> referred to as a Shell sort. Shell-Metzner is a misnomer.
> Signed-off-by: Daniel Dickman <[EMAIL PROTECTED]>
> Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
Why not use the sort routine from lib/so
AsterixTheGaul <[EMAIL PROTECTED]> said:
> > -#define module_init(x) __initcall(x);
> > +#define module_init(x) __initcall(x); __module_init_disable(x);
>
> It would be better if there is brackets around them... like
>
> #define module_init(x) { __initcall(x); __module_init_disable(x); }
>
> the
Sven Luther <[EMAIL PROTECTED]> said:
> On Tue, Apr 05, 2005 at 08:16:48AM -0400, Jeff Garzik wrote:
> > Humberto Massa wrote:
> > >But, the question made here was a subtler one and you are all biting
> > >around the bush: there *are* some misrepresentations of licenses to the
> > >firmware blobs
Jonas Diemer <[EMAIL PROTECTED]> said:
[...]
> I figured there could be a kernel compiled-in option that will make the
> kernel lock all drives found during bootup. then, a malicous program
> would need to install a different kernel in order to harm the drive,
> which would be much more secure.
Wiktor <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
> > Even better: Write a C wrapper for each affected program that just renices
> > it as needed.
> I suggest to implement scalable solution, so the final user wont't have
> to write separate wrapper for *ea
=?iso-8859-1?q?M=E5ns_Rullg=E5rd?= <[EMAIL PROTECTED]> said:
> Wiktor <[EMAIL PROTECTED]> writes:
[...]
> > max renice ulimit is quite good idea, but it allows to change nice of
> > *any* process user has permissions to. it could be implemented also,
> > but the idea of 'nice' file attribute is t
"Jean Delvare" <[EMAIL PROTECTED]> said:
> > > > No, there is a third case: the pointer can be NULL, but the compiler
> > > > happened to move the dereference down to after the check.
> > > Wow. Great point. I completely missed that possibility. In fact I didn't
> > > know that the compiler could
"Jean Delvare" <[EMAIL PROTECTED]> said:
[Sttributions missing, sorry]
> > > Think about it. If the pointer could be NULL, then it's unlikely that
> > > the bug would have gone unnoticed so far (unless the code is very
> > > recent). Coverity found 3 such bugs in one i2c driver [1], and the
>
I'm getting:
CC [M] net/sched/cls_u32.o
net/sched/cls_u32.c: In function `u32_dump':
net/sched/cls_u32.c:778: error: structure has no member named `action'
net/sched/cls_u32.c:778: error: structure has no member named `action'
make[2]: *** [net/sched/cls_u32.o] Error 1
make[1]: *** [n
Kyle Moffett <[EMAIL PROTECTED]> said:
[...]
> I think it really depends on the APIs implemented. Anything based
> on the sysfs code, even if only using the APIs, will probably be
> found to be a derivative work (NOTE: IANAL) because the sysfs API
> is so very different from everything else. Ot
Steven Rostedt <[EMAIL PROTECTED]> said:
> On Sun, 2005-03-27 at 21:54 -0400, Horst von Brand wrote:
[...]
> > Wrong. You are free to do whatever you like in the privacy of your home,
> > but not distribute the result. So you could very well distribute both
> > piece
Kyle Moffett <[EMAIL PROTECTED]> said:
> On Mar 27, 2005, at 14:16, Aaron Gyes wrote:
> > So what? Sure, GPL'd drivers are easier for an end-user in that case.
> > What does that have to do with law?
> Well, under most interpretations of the GPL, you are *NOT* allowed to
> even _link_ non-GPL code
Dave Jones <[EMAIL PROTECTED]> said:
> On Sun, Mar 27, 2005 at 05:12:58PM +0200, Jan Engelhardt wrote:
>
> > Well, kfree inlined was already mentioned but forgotten again.
> > What if this was used:
> >
> > inline static void kfree_WRAP(void *addr) {
> > if(likely(addr != NULL)) {
> >
Marcin Dalecki <[EMAIL PROTECTED]> said:
> On 2005-03-27, at 00:21, linux-os wrote:
> > Always, always, a call will be more expensive than a branch
> > on condition.
Wrong.
> > It's impossible to be otherwise.
Many, many counterexamples say otherwise...
> >
Linus Torvalds <[EMAIL PROTECTED]> said:
> On Thu, 3 Mar 2005, Horst von Brand wrote:
> > [I'm pulling bk daily, and have it mixed with the ipw tree too, so I'm just
> > the kind of tester you are looking for... haven't seen any of the
> > showstopper bu
Linus Torvalds <[EMAIL PROTECTED]> said:
> On Wed, 2 Mar 2005, Jeff Garzik wrote:
> > If we want a calming period, we need to do development like 2.4.x is
> > done today. It's sane, understandable and it works.
> No. It's insane, and the only reason it works is that 2.4.x is a totally
> differen
Lee Revell <[EMAIL PROTECTED]> said:
> On Tue, 2005-03-01 at 12:20 -0800, Ben Greear wrote:
[...]
> > What happens if you just don't muck with the NIC and let it auto-negotiate
> > on it's own?
> This can be asking for trouble too (auto negotiation is often buggy).
I'be seen much more broken ne
"Randy.Dunlap" <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
> > "David S. Miller" <[EMAIL PROTECTED]> said:
> >>On Mon, 28 Feb 2005 17:07:43 -0300
> >>Horst von Brand <[EMAIL PROTECTED]> wrote:
> > [...]
> >>&g
"David S. Miller" <[EMAIL PROTECTED]> said:
> On Mon, 28 Feb 2005 17:07:43 -0300
> Horst von Brand <[EMAIL PROTECTED]> wrote:
[...]
> > So, either the dependencies have to get fixed so floppy can't be modular
> > for this architecture, or the releva
As things stand today, floppy can't be modular (even though the
configuration allows it!) because drivers/block/floppy.c references stuff
in arch/sparc64/kernel/entry.S which isn't included if the floppy
isn't. But that same code references symbols in floppy.c, so it doesn't
help making it depend o
[EMAIL PROTECTED] said:
> Surlignage Russell King <[EMAIL PROTECTED]>:
> > On Mon, Feb 28, 2005 at 02:13:57PM +0100, [EMAIL PROTECTED] wrote:
> > > NPAR times :-). As I stated, npar is unsigned.
> > I think that's disgusting then - it isn't obvious what's going on, which
> > leads to mistakes.
>
linux-os <[EMAIL PROTECTED]> said:
> On Fri, 25 Feb 2005, Payasam Manohar wrote:
> > I tried to insert a sample module into Fedora core 2 , But it is giving
> > an error message that " no module in the object"
> > The same module was inserted successfully into Redhat linux 9.
> > Is there any chan
Brian Gerst <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
> > Brian Gerst <[EMAIL PROTECTED]> said:
> >
> >>- Make sprintf call vsnprintf directly
> >>- use INT_MAX for sprintf and vsprintf
> > This is the size limit on what is written. 4
"Randy.Dunlap" <[EMAIL PROTECTED]> said:
> Stuart MacDonald wrote:
[...]
> > So what I'm wondering is, is there a location on the net where Linus'
> > statements about how the kernel is to be are collected? ie, Where the
> > above statements could all be found, with cites.
> >
> > I'm thinking t
Brian Gerst <[EMAIL PROTECTED]> said:
> - Make sprintf call vsnprintf directly
> - use INT_MAX for sprintf and vsprintf
This is the size limit on what is written. 4GiB sounds a bit extreme...
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica
Here (sparc64) I get build failures due to EXTRA_CFLAGS being set in
arch/sparc64/kernel/Makefile:
EXTRA_CFLAGS := -Werror
But if I override this setting (broken, filesistems use clear_user(),
discard the result and have comments justifiying this) on the make run like
make EXTRA_CFLAGS= all
Hugh Dickins <[EMAIL PROTECTED]> said:
> On Wed, 23 Feb 2005, Ammar T. Al-Sayegh wrote:
> > I recently installed Fedora RC3 on a new server.
> > The kernel is 2.6.10-1.741_FC3smp.
> I can't really speak for Fedora RC3 kernels,
> perhaps there's some special patch in there that happens to
> trigger
Machine is sparc64, bk of today, gcc-3.4.2-6.fc3 (Aurora Corona). First 2.6
I try to build here, so it might be something known.
Build fails due to -Werror with:
include/asm/uaccess.h: In function `load_elf_binary':
arch/sparc64/kernel/../../../fs/binfmt_elf.c:811: warning: ignoring return
value
Chris Friesen <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
> > Anthony DiSante <[EMAIL PROTECTED]> said:
> >>That's one of the things I asked a few messages ago. Some people on
> >>the list were saying that it'd be "really hard
It is defined in:
include/linux/limits.h:#define NR_OPEN 1024
include/linux/fs.h:#define NR_OPEN (1024*1024) /* Absolute upper limit on fd
num */
One is surely wrong?
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica
Anthony DiSante <[EMAIL PROTECTED]> said:
> linux-os wrote:
> > There has been some discussion that these hung
> > states could be "fixed", but that's absolutely
> > positively incorrect.
> That's one of the things I asked a few messages ago. Some people on the
> list were saying that it'd be "r
[EMAIL PROTECTED] said:
> On Mon, Feb 21, 2005 at 04:53:06PM +0100, Andrea Arcangeli wrote:
[...]
> > AFIK all other SCM except arch and darcs always modify the repo, I never
> > heard complains about it, as long as incremental backups are possible
> > and they definitely are possible.
> Well, a
"Sean" <[EMAIL PROTECTED]> said:
[...]
> Yeah, I didn't mean to suggest that it be opened up to the public :o)
> Just that the flow of information wouldn't all have to originate in bk to
> make it into head (ie. bk could pull changes from head too).
No problem. bk can happily import patches, w
"Sean" <[EMAIL PROTECTED]> said:
> On Thu, February 17, 2005 3:52 pm, Horst von Brand said:
[...]
> > "Best tool for the job" certainly includes minutiae like "benefits" and
> > "price".
> Thank you, that's my point. It'
Clemens Schwaighofer <[EMAIL PROTECTED]> said:
> On 02/17/2005 01:57 PM, Theodore Ts'o wrote:
> > Compare the number of developers, the number of overlapping
> > simultaneous development trees, and the number of patches that touch
> > overlapping files, and you'll begin to start to appreciate the
>
"Sean" <[EMAIL PROTECTED]> said:
> On Thu, February 17, 2005 11:55 am, Chris Friesen said:
> > If you look at the archives, there have been a *lot* of people saying
> > very much the same thing as you. I suspect people are getting tired of
> > giving the same responses all the time.
> >
> > Here i
Andrew Morton <[EMAIL PROTECTED]> said:
> Parag Warudkar <[EMAIL PROTECTED]> wrote:
[...]
> > Is there a reason X86_64 doesnt have CONFIG_FRAME_POINTER anywhere in
> > the .config?
> No good reason, I suspect.
Does x86_64 use up a (freeable) register for the frame pointer or not?
I.e., does -f
Marcin Dalecki <[EMAIL PROTECTED]> said:
> On 2005-02-14, at 19:56, Larry McVoy wrote:
> > All we are trying to do is
> >
> > 1. Provide the open source community with a useful tool.
> > 2. Prevent that from turning into the open source community
> > creating a clone of our tool.
Nicolas Pitre <[EMAIL PROTECTED]> said:
> On Wed, 9 Feb 2005, Larry McVoy wrote:
> > On Wed, Feb 09, 2005 at 05:06:02AM -0200, Alexandre Oliva wrote:
> > > So you've somehow managed to trick most kernel developers into
> > > granting you power over not only the BK history
> > It's exactly the same
Clemens Schwaighofer <[EMAIL PROTECTED]> said:
[...]
> but to be honest, most times I need vfat, and I actually haven't
> encountered a time when I need msdos.
But writing MSDOS on a VFAT filesystem is a sure way to screw it up, and
AFAIU vice-versa.
--
Dr. Horst H. von Brand
"Randy.Dunlap" <[EMAIL PROTECTED]> said:
> Chris Friesen wrote:
[...]
> > If you look at the big chip manufacturers (TI, Maxim, Analog Devices,
> > etc.) they publish specs on everything. It would be nice if others did
> > the same.
> One of the arguments that I have heard is fairly old and d
jerome lacoste <[EMAIL PROTECTED]> said:
> Bernd Eckenfels <[EMAIL PROTECTED]> said:
> >> Could a hardware failure look like bad sectors to fsck?
> > A failure of the bus or a former sporadic error can cause defective fs, but
> > normally you have a read error in fsck no structure error.
> >
> >
Andreas Gruenbacher <[EMAIL PROTECTED]> said:
[...]
> Yes, because a custom swap routine isn't very useful generally. It's
> over-engineered IMHO.
It shouldn't swap, but juggle elements around like so:
t --->+
^ |
| v
x <-- x <-- x <--
Matt Mackall <[EMAIL PROTECTED]> said:
> This patch series introduced a new pair of CONFIG_EMBEDDED options call
> CONFIG_BASE_FULL/CONFIG_BASE_SMALL. Disabling CONFIG_BASE_FULL sets
> the boolean CONFIG_BASE_SMALL to 1 and it is used to shrink a number
> of core data structures. The space savings
Matt Mackall <[EMAIL PROTECTED]> said:
> This patch adds a generic array sorting library routine. This is meant
> to replace qsort, which has two problem areas for kernel use.
Another problem is the GPL license. It will certainly be wanted from
non-GPL (e.g., binary) modules. Please just EXPORT_SY
Lorenzo =?ISO-8859-1?Q?Hern=E1ndez_?=
=?ISO-8859-1?Q?Garc=EDa-Hierro?= <[EMAIL PROTECTED]> said:
> Attached you can find a split up patch ported from grSecurity [1], as
> Linus commented that he wouldn't get a whole-sale patch, I was working
> on it and also studying what features of grSec
Julien TINNES <[EMAIL PROTECTED]> said:
> Not very important but ((get_random_int() % 4096) << 4) could be
> optimized into get_random_int() & 0xFFF0.
Check first if the compiler doesn't do it by itself.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Infor
[EMAIL PROTECTED] (H. Peter Anvin) said:
[...]
> In klibc, I use combsort:
>
> /*
> * qsort.c
> *
> * This is actually combsort. It's an O(n log n) algorithm with
> * simplicity/small code size being its main virtue.
> */
>
> #include
> #include
>
> static inline size_t newgap(size_t g
"Rafael J. Wysocki" <[EMAIL PROTECTED]> said:
[...]
> To be precise, one needs ~(log N) of stack space for qsort, and frankly, one
> should use something like the shell (or should I say Shell?)
Shell. It is named for a person.
> sort
Matt Mackall <[EMAIL PROTECTED]> said:
> On Sun, Jan 23, 2005 at 03:39:34AM +0100, Andi Kleen wrote:
[...]
> > -Andi (who thinks the glibc qsort is vast overkill for kernel purposes
> > where there are only small data sets and it would be better to use a
> > simpler one optimized for code size)
Andreas Gruenbacher <[EMAIL PROTECTED]> said:
> Signed-off-by: Andreas Gruenbacher <[EMAIL PROTECTED]>
> Acked-by: Olaf Kirch <[EMAIL PROTECTED]>
[...]
> +/* Order size using quicksort. This implementation incorporates
> + four optimizations discussed in Sedgewick:
> +
> + 1. Non-recursive,
Carl Spalletta <[EMAIL PROTECTED]> said:
> >From http://www.linuxrd.com/~carl/cgi-bin/lnxtc.pl?help
[...]
> "It works, in part, by expanding function-yielding macros and by mangling
> function names with the name of the file containing the function's
> definition, prior to creating the cscope fil
Chris Wright <[EMAIL PROTECTED]> said:
[...]
> DRAFT
[...]
> It is preferred that mail sent to the security team is encrypted
> with $PUBKEY.
Note that $PUBKEY might change, give pointers to the canonical places where
you can get the latest version (latest kernel source?). Perhaps indicate
emove and
> re-insert the dcache entry. Right?
If they are unreferenced, they can be dropped without much cost. The
problem is what to do if you have 40 pages, each 1/10 filled with data in
active use.
--
Horst von Brand http://counter.li.org # 22616
-
To unsubscribe f
Alan Shutko <[EMAIL PROTECTED]> said:
> One more tidbit: ISO/IEC 9899:1990 3.14
>
> 3.14 object: A region of data storage in the execution environment,
> the contents of which can represent values. Except for
> bit-fields, objects are composed of contiguous sequences of one or
> mo
e:
"This is a nice long string
that just goes on
and on\n"
which is illegal in C AFAIU. It does not object to:
"This long string"
"spans several lines, "
"but legally.\n"
The first form does/did appear in several asm()s. Fi
ut there still is a lot of stuff
that needs a more reasonable solution, so no thanks for now.
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
-
To unsubscribe from this list: send the line "unsub
1 - 100 of 297 matches
Mail list logo
