* Re: [ISN] Music file flaws could threaten traders
From: Paul Krumviede @ 2002-12-19 22:41 UTC (permalink / raw)
To: Russell Coker, selinux
In-Reply-To: <200212192307.20386.russell@coker.com.au>
--On Thursday, 19 December, 2002 23:07 +0100 Russell Coker
<russell@coker.com.au> wrote:
> This type of thing could affect Linux in the same way as it affects
> Windows.
i'm not so sure. the bugtraq posting about the windows XP bug
indicated that it could be exploited even without downloading
a file to the user's computer. if using explorer, the file had to be
on the local machine, but didn't need to be "played" to allow
an exploit. i don't think that either case is relevant to selinux
(but would like to know if i'm wrong).
i haven't looked at the winamp report yet.
-paul
> Currently we have "risky" programs such as netscape, games, and IRC
> clients in their own domains that have types for read-only and for
> read-write files (and no ability to run gpg or other important programs).
>
> The problem about doing the same for audio/video programs such as players
> for avi, mp3, and vob files is that their typical use involves
> downloading files from the net to play immediately so that denying them
> read access to user_home_t files will give a large decrease in
> functionality. I believe that there are two major categories of SE
> Linux users, those who will never run such A/V programs on Linux, and
> those who won't use any security software that gets in the way of their
> entertainment.
>
> So I think that having a domain for A/V programs such as $1_av_t that has
> read access to $1_home_t and can create files with the type $1_home_av_t
> may not be as tightly secured as we might like, but the people who are
> concerned about that won't use it anyway.
>
> On Thu, 19 Dec 2002 09:58, InfoSec News wrote:
>> http://news.com.com/2100-1001-978403.html?tag=fd_top
>>
>> By Robert Lemos
>> Staff Writer, CNET News.com
>> December 18, 2002, 5:12 PM PT
>>
>> A security firm on Wednesday warned that people using Windows XP or
>> popular music player WinAmp could fall prey to a vulnerability,
>> enabling a modified music file to take control of a person's PC.
>
> --
> http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/~russell/ My home page
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
> with the words "unsubscribe selinux" without quotes as the message.
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply
* Re: RFC: bus_type and device_class merge (or partial merge)
From: Adam J. Richter @ 2002-12-19 22:44 UTC (permalink / raw)
To: mochel; +Cc: linux-kernel
>> = Adam Richter
> = Patrick Mochel
>> I'm thinking about trying to embed struct device_class into
>> struct bus_type or perhaps just eliminate the separate struct
>> bus_type. The two structures are almost identical, especially
>> considering that device_class.devnum appears not to be used by
>> anything.
>
>Someone else tried to do this a while back, and my argument was the same
>as this is going to be: they are very distinct objects that describe
>different things.
A philosophical musing is not substitute for identifying real
technical advantages or disadvantages, but thanks for the response.
If my proposed changes shrink kernel memory footprint, improve
code maintainability, allow multiple drivers per device (e.g., scsi
generic and scsi disk), users will be better off with those advantages
than being lost in a doctrine for which they've lost track of the benefits.
Also, thanks for the pointer to the paper. I've only skimmed
it at this point, but it at already has helped clarify your thinking
on struct subsystem for me.
>They're not the same, though. They may be similar, but they are
>fundamentally different.
There are also differences between USB and PCI, but that
doesn't mean that the part that is handled by drivers/base has to be
different. The question is whether having separate implementations
for a set of differences make the code smaller, faster, more
functional, or delivers other real benefits that tip the trade-off.
>A class is the flipside. It describes the function a device is designed
>to perform, independent of its underlying transport.
You see it as the "flipside" because you're used to seeing
only two levels of indirection (you also haven't shown a real benefit
to a different interface). Let's look at your example:
>Consider audio devices. The only things I care about are /dev/mixer and
>/dev/dsp, which map to devices registered with the audio subsystem.
>Actually, what is registered are not devices. They are objects allocated
>by the driver for my sound card that describe the device in the context of
>the audio subsystem. This object is independent of the bus the device
>resides on. Communication from userspace to the device passes through the
>driver, which formats the class requests to bus and device-specific ones
>to actaully talk to the physical device. Something like this:
>
>
> Me -> device node -> kernel intf -> audio subsys -> driver -> bus -> device
Even in this example, there could be many gradations between
bus_type and device_class. There can be hardware support for complex
sound synthesis and there can be software versions of that same
interface to support more ordinary sound cards. Sound cards are a
good example of a type of device that can have separate but related
functions, so it may be handy to have device drivers that are written
to accomodate multiple drivers per device (although I would agree that
the _default_ policy should remain only one driver per device at this
point). The audio hardware may also be located across multiple busses
(PCI --> USB --> USB audio) or may involve more software (PC speaker
driver).
Perhaps it would help you to understand the impetus that made
me think about this. I want to have a mechanism for race-free module
unloading without a new lowest level locking primitive (i.e., just by
using rw_semaphore). To make its use transparent for most cases, I
want add a field to struct device_driver and add a couple of lines to
{,un}register_driver, and I see that if I have to duplicate this
effort if I want the same thing for, say, converting filesystems to
use the generic driver interface. I don't see that duplication buying
any real improvement in speed, kernel footprint, source code size,
etc. In other words, having two separate interfaces makes it harder
to write other facilities that are potentially generic to
driver/target rendezvous.
Anyhow, if you don't convince me of the error of my ways, then
it's probably incumbent upon me to produce a patch before whining
further.
>Consolidation is possible, but I would not recommend doing it by merging
>the structures. Look for other ways to create common objects that the two
>can share.
I'm thinking about this. I just wonder if there would be any
remaining fields that would not be common.
>The distinction between the object types is important,
>conceptually, if nothing else.
If it is not important for any other reason, then it's just a
lost opportunity for code shrink and perhaps for potentially making
the facility generically useful in new ways.
>Especially during the continuing evolution
>of the model. At least for now, and for probably a very long time, I will
>not consider patches to consolidate the two object types.
Linux will be better if we decide things by weighing technical
benefits rather than by attempts at diktat. I recommend you keep an
open mind about it.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
^ permalink raw reply
* Re: [BENCHMARK] scheduler tunables with contest - prio_bonus_ratio
From: Robert Love @ 2002-12-19 22:46 UTC (permalink / raw)
To: Con Kolivas; +Cc: linux kernel mailing list
In-Reply-To: <200212200850.32886.conman@kolivas.net>
On Thu, 2002-12-19 at 16:50, Con Kolivas wrote:
> Changing this tunable seems to shift the balance in either direction depending
> on the load. Most of the disk writing loads have shorter times as pb goes up,
> but under heavy mem_load the time goes up (without an increase in the amount
> of work done by the mem_load itself). The effect is quite large.
This is one of the most interesting tests. Thanks, Con.
prio_bonus_ratio determines how big a bonus we give to interactive
tasks, as a percentage of the full -20 to +19 nice range. Setting it to
zero means we scale the bonuses/penalties be zero percent, i.e. we do
not give a bonus or penalty. 25% implies 25% of the range is used (i.e.
-/+5 points). Etc.
I suspect tests where you see an improvement as the value increases are
ones in which the test is more interactive than the background load. In
that case, the larger bonuses helps more so to the test and it completes
quicker.
When you see a decrease associated with a larger value, the test is less
interactive than the load. Thus the load is scheduled to the detriment
of the test, and the test takes longer to complete.
Not too sure what to make of it. It shows the interactivity estimator
does indeed help... but only if what you consider "important" is what is
considered "interactive" by the estimator. Andrew will say that is too
often not the case.
Robert Love
P.S. This setting is also useful for endusers to test. Setting
prio_bonus_ratio to zero effectively disables the interactivity
estimator, so users can test without that feature enabled. It should
fix e.g. Andrew's X wiggle issue.
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Pavel Machek @ 2002-12-19 0:14 UTC (permalink / raw)
To: Rogier Wolff
Cc: Linus Torvalds, Ulrich Drepper, Alan Cox, Matti Aarnio,
Hugh Dickins, Dave Jones, Ingo Molnar, Linux Kernel Mailing List,
hpa
In-Reply-To: <20021218135722.A15645@bitwizard.nl>
Hi!
> > > But this is exactly what I expect to happen. If you want to implement
> > > gettimeofday() at user-level you need to modify the page.
> >
> > Note that I really don't think we ever want to do the user-level
> > gettimeofday(). The complexity just argues against it, it's better to try
> > to make system calls be cheap enough that you really don't care.
>
> I'd say that this should not be "fixed" from userspace, but from the
> kernel. Thus if the kernel knows that the "gettimeofday" can be made
> faster by doing it completely in userspace, then that system call
> should be "patched" by the kernel to do it faster for everybody.
>
> Next, someone might find a faster (full-userspace) way to do some
> "reads"(*). Then it might pay to check for that specific
> filedescriptor in userspace, and only call into the kernel for the
> other filedescriptors. The idea is that the kernel knows best when
> optimizations are possible.
>
> Thus that ONE magic address is IMHO not the right way to do it. By
> demultiplexing the stuff in userspace, you can do "sane" things with
> specific syscalls.
>
> So for example, the code at 0xffff80000 would be:
> mov 0x00,%eax
> int $80
> ret
>
> (in the case where sysenter & friends is not available)
This could save that one register needed for 6-args syscalls. If code
at 0xffff8000 was mov %ebp, %eax; sysenter; ret for P4, you could do
6-args syscalls this way.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
^ permalink raw reply
* Re: Domain transition -- enabling user_r in eklogin
From: Russell Coker @ 2002-12-19 22:33 UTC (permalink / raw)
To: Jesse Pollard; +Cc: SELinux
In-Reply-To: <200212190802.33560.pollard@admin.navo.hpc.mil>
On Thu, 19 Dec 2002 15:02, Jesse Pollard wrote:
> > It's the same thing. If I can trick you into running some arbitary
> > commands with your main role then I can get your ssh identity key and
> > your gpg secret key. These crypto keys are often worth more than the
> > hardware that they are stored on...
>
> Only if access is permitted to be over an unsecured channel.
>
> The differentation between a local user and a remote user has to be
> provided.
The "if I can trick you" part means that the distinction between local and
remote logins is probably not relevant. Consider that you meet someone in
Starbucks and say "there's this really cool program at www.foo.com" which
they then download and run...
Of course we could deny execute access to user_home_t but variations on the
same theme can always be used while there are users who can be tricked and
net access for easy back-channels.
> Access to the secret key(s) probably should not be permitted from an
> unsecured location/connection. This does require network labels to work.
I guess you could have different roles, and have sshd only allow transitioning
to a low security role which is prohibited from running ssh or gpg. I wonder
whether a domain that only has full access to user_home_dir_t and user_home_t
can misdirect the actions of ssh or gpg...
I don't think that network labels allow us to do anything productive in this
regard as network operations are so abstracted. When a KDE ioslave can talk
to a http proxy to get access to the outside network then making real use of
network labels without seriously reducing functionality is almost impossible.
For my aims a significant reduction in functionality is unacceptable.
> It does mean that the plugin for checking PGP signatures (at a minimum the
> one for generating signatures) would have to be sufficiently separate from
> the netscape process to be labeled separately. It could not use loadable
> modules, for instance. It also means any scripts started should not have
> access either.
The problem is that if you can run GPG currently you can encrypt the secret
key to yourself with a password (IE not encrypting to a public key) and then
decrypt the result to get the key. A future version of GPG will address
this. I don't know how PGP performs in this regard.
> This is not a 100% solution - If netscape is used to download an
> application, then the user proceeds to configure/compile/run then all bets
> are off since the users actions are overriding the labels. It should/could
> prevent a trojan from passing the files out though - it would not be
> authorized access to the secret key(s) or the Kerberos ticket cache. Only
> trusted utilities would have that capability.
However if the ticket can't be used on other machines then the concern is not
that it will be passed out, but that a process holding the ticked will be
controlled by a program that is a proxy running on behalf of a program
outside.
One of my friends wrote a nifty set of CGI scripts to run a terminal session
through a web page using standard web forms functionality. It wouldn't be
THAT much more difficult to do it the other way around and have machine
running bash be the HTTP client and the HTTP server have the client side of
the shell session.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply
* Re: Dedicated kernel bug database
From: Hanna Linder @ 2002-12-19 22:45 UTC (permalink / raw)
To: mbligh; +Cc: Eli Carter, Randy.Dunlap, linux-kernel
In-Reply-To: <3E0240CA.4000502@inet.com>
> Bug tracking can get much better (I _hope_!), but I expect it to take some beating on the problem. Keep beating on it.
OK. Since we are on the topic. I have some (intending to be) constructive
criticisms for the owners of the 2.5 kernel tracker site (not sure exactly
who they are but I know mbligh is part of it).
Why are bugs automatically assigned to owners?
If there was an unassigned category that would make it
easy to query.
How else are those of us who want to help stabilize the 2.5 kernel supposed
to know which bugs are being worked on and which are not?
(Please dont tell me "email". Am I really supposed to email every
person who has a bug asking if they are really working on it or not?)
Could you make a list of all the people who have volunteered to be
bugtracker maintainers and their respective kernel pieces.
Also a list of people who arent maintainers but are available to help
could be useful for the owners to assign bugs to.
Thanks.
Hanna
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: H. Peter Anvin @ 2002-12-19 22:36 UTC (permalink / raw)
To: Pavel Machek
Cc: dean gaudet, Linus Torvalds, Dave Jones, Ingo Molnar,
linux-kernel
In-Reply-To: <20021219223451.GG17941@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
> Hi!
>
>
>>>User on cpu1 reads time, communicates it to cpu2, but cpu2 is drifted
>>>-50ns, so it reads time "before" time reported cpu1. And gets confused.
>>>
>>
>>How can you get that communication to happen in < 50 ns?
>
>
> I'm not sure I can do that, but I'm not sure I can't either. CPUs
> snoop each other's cache, and that's supposed to be fast...
>
Even over a 400 MHz FSB you have 2.5 ns cycles. I doubt you can
transfer a cache line in 20 FSB cycles.
-hpa
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Pavel Machek @ 2002-12-19 22:34 UTC (permalink / raw)
To: H. Peter Anvin
Cc: Pavel Machek, dean gaudet, Linus Torvalds, Dave Jones,
Ingo Molnar, linux-kernel
In-Reply-To: <3E024880.4010802@transmeta.com>
Hi!
> > User on cpu1 reads time, communicates it to cpu2, but cpu2 is drifted
> > -50ns, so it reads time "before" time reported cpu1. And gets confused.
> >
>
> How can you get that communication to happen in < 50 ns?
I'm not sure I can do that, but I'm not sure I can't either. CPUs
snoop each other's cache, and that's supposed to be fast...
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
^ permalink raw reply
* [BUG] oops in dcache.c , 2.4.20
From: Nils O. Selåsdal @ 2002-12-19 22:34 UTC (permalink / raw)
To: linux-kernel
Recently upgraded a little box from 2.4.20-pre3 to 2.4.20, and after 2
days it locked up, and the following oops occured:
Dec 19 03:41:13 lfs kernel: kernel BUG at dcache.c:345!
Dec 19 03:41:13 lfs kernel: invalid operand: 0000
Dec 19 03:41:13 lfs kernel: CPU: 0
Dec 19 03:41:13 lfs kernel: EIP: 0010:[prune_dcache+78/336] Not
tainted
Dec 19 03:41:13 lfs kernel: EFLAGS: 00010206
Dec 19 03:41:13 lfs kernel: eax: 00020000 ebx: c0d76e78 ecx:
000008c5 edx: c0d76ef8
Dec 19 03:41:13 lfs kernel: esi: c0d76e60 edi: c02d1f18 ebp:
00000049 esp: c0039f60
Dec 19 03:41:13 lfs kernel: ds: 0018 es: 0018 ss: 0018
Dec 19 03:41:13 lfs kernel: Process kswapd (pid: 5, stackpage=c0039000)
Dec 19 03:41:13 lfs kernel: Stack: 0000000e 000001d0 00000018 00000006
c0147f65 000001b1 c012f9a1 00000006
Dec 19 03:41:13 lfs kernel: 000001d0 c0257cc0 00000006 000001d0
c0257cc0 00000000 c012f9f0 00000020
Dec 19 03:41:13 lfs kernel: c0257cc0 00000000 c0038000 c012fb00
c0257cc0 00000000 c0038245 0008e000
Dec 19 03:41:13 lfs kernel: Call Trace: [shrink_dcache_memory+37/64]
[shrink_caches+97/128] [try_to_free_pages_zone+48/80]
[kswapd_balance_pgdat+80/160] [kswapd_balance+22/48]
Dec 19 03:41:13 lfs kernel: Code: 0f 0b 59 01 71 c4 22 c0 8d 43 f8 8b 53
f8 8b 48 04 89 4a 04
Using defaults from ksymoops -t elf32-i386 -a i386
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 0f 0b ud2a
Code; 00000002 Before first symbol
2: 59 pop %ecx
Code; 00000003 Before first symbol
3: 01 71 c4 add %esi,0xffffffc4(%ecx)
Code; 00000006 Before first symbol
6: 22 c0 and %al,%al
Code; 00000008 Before first symbol
8: 8d 43 f8 lea 0xfffffff8(%ebx),%eax
Code; 0000000b Before first symbol
b: 8b 53 f8 mov 0xfffffff8(%ebx),%edx
Code; 0000000e Before first symbol
e: 8b 48 04 mov 0x4(%eax),%ecx
Code; 00000011 Before first symbol
11: 89 4a 04 mov %ecx,0x4(%edx)
Dec 19 19:20:52 lfs kernel: Intel Pentium with F0 0F bug - workaround
enabled.
Lines right before the oops in the syslog were:
Dec 18 14:10:00 lfs fcron[1196]: Job /sbin/rmmod -as ; /sbin/rmmod -as ;
/sbin/rmmod -as ; /sbin/rmmod -as started for user root (pid 1197)
Dec 19 03:34:00 lfs fcron[1202]: Job /usr/sbin/logrotate
/etc/logrotate.conf started for user root (pid 1203)
Dec 19 03:40:00 lfs fcron[1204]: Job updatedb started for user root (pid
1205)
The box is using reiserfs all over, and the 2.4.20 is compiled with gcc
3.2.1, got 16MB ram.
And its using a 2.5" harddisk from a laptop if it matters.
noselasd:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 2
model name : Pentium 75 - 200
stepping : 6
cpu MHz : 119.755
fdiv_bug : no
hlt_bug : no
f00f_bug : yes
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 238.38
noselasd:~$ cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 430FX - 82437FX TSC [Triton I] (rev 2).
Master Capable. Latency=64.
Bus 0, device 7, function 0:
ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 2).
Bus 0, device 8, function 0:
VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev
0).
IRQ 11.
Non-prefetchable 32 bit memory at 0xff000000 [0xff7fffff].
The box also locked up one more time, when moving 1500 mails to an IMAP
folder on the machine. No oops in the log this time, but when rebooting
it oopsed when replaying the (reiserfs) log on the / filesystem.
Switched back to 2.4.20-pre3 and it works fine.
--
Nils Olav Selåsdal <NOS@Utel.no>
System Developer, UtelSystems a/s
w w w . u t e l s y s t e m s . c o m
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: H. Peter Anvin @ 2002-12-19 22:30 UTC (permalink / raw)
To: Pavel Machek
Cc: dean gaudet, Linus Torvalds, Dave Jones, Ingo Molnar,
linux-kernel
In-Reply-To: <20021219222614.GE17941@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
>
> User on cpu1 reads time, communicates it to cpu2, but cpu2 is drifted
> -50ns, so it reads time "before" time reported cpu1. And gets confused.
>
How can you get that communication to happen in < 50 ns?
-hpa
^ permalink raw reply
* Re: An array failover driver
From: Steve Ralston @ 2002-12-19 22:24 UTC (permalink / raw)
To: Qi, Yanling; +Cc: 'linux-scsi-reflector'
In-Reply-To: <EB1DF7EA0D32D611B79C0002A51363F194A7BE@exw-ks.ks.lsil.com>
On 12/19/2002 03:56 PM, Qi, Yanling wrote:
>Hi All,
>
>I am going to develop a multiple-pathing driver to support our storage array
>hardware on Linux(2.4 and later). I prefer the driver sit on the top of HBA
>drivers (fibre channel adapter drivers) and below middle level (the unifying
>layer). In other words, insert my pseudo driver into middle level and lower
>level drivers. The driver will take care of path failover. I am still in
>research phase. Do you have any suggestions?
>
>
I've been there & done that, for drivers/message/fusion drivers (aka for
FC9x9 HABs).
The dynamic multi-pathing failover driver I wrote acted as sort of a shim,
sitting logically between the scsi midlayer and {mptbase+mptscsih}
driver(s),
sort of exactly as you describe above. The source is available via:
ftp://ftp.lsil.com/pub/symchips/fibre_ch/Metastor/dmpath-2.01x25.tar.gz
Which HBA driver are you looking at doing this for?
^ permalink raw reply
* Re: [PATCH]: for poor sools with old I2 & 64 bits kernel
From: Thiemo Seufer @ 2002-12-19 22:22 UTC (permalink / raw)
To: Juan Quintela; +Cc: Ralf Baechle, mipslist
In-Reply-To: <m2r8cdhel4.fsf@demo.mitica>
Juan Quintela wrote:
[snip]
> >> Notice that I am using egcs for MIPS64 as I am not able to compile the
> >> kernel with gcc-3.2 :(
>
> thiemo> I don't think this is compiler dependent. :-)
>
> from arch/mips64/Makefile:
>
> #
> # Some machines like the Indy need 32-bit ELF binaries for booting purposes.
> # Other need ECOFF, so we build a 32-bit ELF binary for them which we then
> # convert to ECOFF using elf2ecoff.
Argh, this hack again! Sorry for the confusion, I'm just used to think
64bit == ELF64.
Thiemo
^ permalink raw reply
* How to compil dvb CVS with 2.5.52?
From: Gregoire Favre @ 2002-12-19 22:27 UTC (permalink / raw)
To: linux-dvb; +Cc: linux-kernel
Hello,
I am too stupid to understand the README: with 2.5.52 should I patch
with both :
greg@localhost:linux >patch -p1 < /usr/src/CVS/dvb-kernel/00_knorr_v4l1_compat.patch
patching file drivers/media/video/Makefile
Hunk #1 succeeded at 5 with fuzz 1.
patching file drivers/media/video/v4l1-compat.c
patching file kernel/ksyms.c
Hunk #1 succeeded at 323 (offset 2 lines).
greg@localhost:linux >patch -p1 < /usr/src/CVS/dvb-kernel/01_video-buf.patch
patching file drivers/media/Makefile
patching file drivers/media/Kconfig
patching file drivers/media/common/Kconfig
patching file drivers/media/common/Makefile
patching file drivers/media/common/video-buf.c
patching file drivers/media/common/video-buf.h
patching file drivers/media/video/Makefile
Hunk #2 succeeded at 38 with fuzz 2.
patching file drivers/media/video/saa7134/Makefile
patching file drivers/media/video/video-buf.c
patching file drivers/media/video/video-buf.h
And then the makelinks /usr/src/linux-2.5.52-dvb
It then don't compil and i have to patch with the patch sent to this
list the Wed, 11 Dec 2002 10:53:43 +1100 from Rusty Russell:
--- drivers/media/dvb/dvb-core/dvb_i2c.c 2002-12-19 23:21:07.000000000 +0100
+++ drivers/media/dvb/dvb-core/dvb_i2c.c~ 2002-11-28 19:57:09.000000000 +0100
@@ -64,8 +64,10 @@
void try_attach_device (struct dvb_i2c_bus *i2c, struct dvb_i2c_device *dev)
{
if (dev->owner) {
- if (!try_inc_mod_count(dev->owner))
+ if (!MOD_CAN_QUERY(dev->owner))
return;
+
+ __MOD_INC_USE_COUNT(dev->owner);
}
if (dev->attach (i2c) == 0) {
And then:
ld -m elf_i386 -r -o drivers/media/common/saa7146.ko drivers/media/common/saa7146_core.o drivers/media/common/saa7146_hlp.o drivers/media/common/saa7146_i2c.o drivers/media/common/saa7146_vbi.o drivers/media/common/saa7146_video.o
make -f scripts/Makefile.build obj=drivers/media/dvb
make -f scripts/Makefile.build obj=drivers/media/dvb/av7110
make[4]: *** No rule to make target `drivers/media/dvb/av7110/saa7146_core.s', needed by `drivers/media/dvb/av7110/saa7146_core.o'. Stop.
make[3]: *** [drivers/media/dvb/av7110] Error 2
make[2]: *** [drivers/media/dvb] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
>From my .config:
CONFIG_DVB=y
CONFIG_DVB_CORE=y
CONFIG_DVB_DEVFS_ONLY=y
CONFIG_DVB_ALPS_BSRV2=m
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_VIDEOBUF=m
Well, could you explain me what's wrong with my way to compil it?
Thank you very much,
Grégoire
________________________________________________________________
http://ulima.unil.ch/greg ICQ:16624071 mailto:greg@ulima.unil.ch
^ permalink raw reply
* depmod errors in 2.5.52-bk
From: carbonated beverage @ 2002-12-19 22:23 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
Got tons of depmod errors for various symbols in a few drivers I built as
modules, for such things as: kmalloc, __alloc_pages, schedule, etc.
Attatching the errors as a gzip'd file, as it's rather large.
-- DN
Daniel
[-- Attachment #2: bk-errs.txt.gz --]
[-- Type: application/octet-stream, Size: 4354 bytes --]
^ permalink raw reply
* Re: Dedicated kernel bug database
From: Stephen Wille Padnos @ 2002-12-19 22:23 UTC (permalink / raw)
To: John Bradford; +Cc: Randy.Dunlap, linux-kernel
In-Reply-To: <200212192155.gBJLtV6k003254@darkstar.example.net>
Hmmm.
It seems to me that a kernel bug tracking system has to have a pretty
good knowledge (database) of the kernel(s) it is meant to track.
Essentially, a user who has a problem can usually identify what the
problem is ("my external firewire HD doesn't work"), but not where the
cause may be (interrupts / filesystem drivers / mount tools / scsi
generic / sbp2 / ieee1394 / pci / ACPI / APIC / VM / ...).
So, if a user could enter some keywords for their problem and get a list
of possible subsystems that it depends on (along with maintainers for
those subsystems), we'd be getting somewhere.
For the usb / apic / acpi / rtl8139 problem, I would enter something
like USB keyboard, 8139too, local APIC, IO-APIC, VIA kt333, kernel 2.5.45-51
The wizardly database (knowing what each "leaf device" depends on), then
finds the intersection of subsystems that affect all (or some specified
percentage) of the things the keywords match.
This requires a tree of dependencies (pretty much there - look at what
headers are included in each source file) for each driver.
Of course, there are things that everything depends on (VM), which would
probably want to be left out unless no higher level common ancestor of
the problems can be found.
The trouble with searching a flat bug database is that you have to know
what you're looking for. If the bug tracker actually helped figure out
the problem (where possible, of course), that would be a boon.
John Bradford wrote:
[snip snip]
>>| Overall, though, would you rather be presented with a list of
>>| categories, or a list of people and what parts of the code they
>>| maintain. Personally, I think that a list of people is more
>>| intuitive, rather than an abstract list of categories, but I could be
>>| wrong.
>>
>>Do we have anyone targeted for interrupt routing problems (PIC, IO APIC,
>>ACPI, etc.)?
>>
>>
>
>No. I nominate Alan :-).
>
Agreed. (can he be elected without knowing he's on the ballot? :)
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: H. Peter Anvin @ 2002-12-19 22:26 UTC (permalink / raw)
To: Linus Torvalds
Cc: Jamie Lokier, bart, davej, terje.eggestad, drepper, matti.aarnio,
hugh, mingo, linux-kernel
In-Reply-To: <Pine.LNX.4.44.0212191412180.1629-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>
> Uli's suggested glibc approach is to just put the magis system call
> address (which glibc gets from the AT_SYSINFO elf aux table entry) into
> the per-thread TLS area, which is alway spointed to by %gs anyway.
>
> THIS WORKS WITH ALL DSO'S WITHOUT ANY GAMES, ANY MMAP'S, ANY RELINKING, OR
> ANY EXTRA WORK AT ALL!
>
> The system call entry becomes a simple
>
> call *%gs:constant-offset
>
> Not mmap. No magic system calls. No relinking. Not _nothing_. One
> instruction, that's it.
>
Unfortunately it means taking an indirect call cost for every invocation...
-hpa
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Pavel Machek @ 2002-12-19 22:26 UTC (permalink / raw)
To: H. Peter Anvin
Cc: dean gaudet, Linus Torvalds, Dave Jones, Ingo Molnar,
linux-kernel
In-Reply-To: <3E0246DE.2010608@transmeta.com>
Hi!
> >>>>don't many of the multi-CPU problems with tsc go away because you've got a
> >>>>per-cpu physical page for the vsyscall?
> >>>>
> >>>>i.e. per-cpu tsc epoch and scaling can be set on that page.
> >>>
> >>>Problem is that cpu's can randomly drift +/- 100 clocks or so... Not
> >>>nice at all.
> >>>
> >>
> >>?100 clocks is what... ?50 ns these days? You can't get that kind of
> >>accuracy for anything outside the CPU core anyway...
> >
> > 50ns is bad enough when it makes your time go backwards.
> >
>
> Backwards?? Clock spreading should make the rate change, but it should
> never decrement.
User on cpu1 reads time, communicates it to cpu2, but cpu2 is drifted
-50ns, so it reads time "before" time reported cpu1. And gets confused.
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Linus Torvalds @ 2002-12-19 22:22 UTC (permalink / raw)
To: Jamie Lokier
Cc: bart, davej, hpa, terje.eggestad, drepper, matti.aarnio, hugh,
mingo, linux-kernel
In-Reply-To: <20021219221043.GA18562@bjl1.asuk.net>
On Thu, 19 Dec 2002, Jamie Lokier wrote:
> Linus Torvalds wrote:
> > For _zero_ gain. The jump to the library address has to be indirect
> > anyway, and glibc has several places to put the information without any
> > mmap's or anything like that.
>
> This is not true, (but your overall point is still correct).
Go back and read the postings by Uli.
Uli's suggested glibc approach is to just put the magis system call
address (which glibc gets from the AT_SYSINFO elf aux table entry) into
the per-thread TLS area, which is alway spointed to by %gs anyway.
THIS WORKS WITH ALL DSO'S WITHOUT ANY GAMES, ANY MMAP'S, ANY RELINKING, OR
ANY EXTRA WORK AT ALL!
The system call entry becomes a simple
call *%gs:constant-offset
Not mmap. No magic system calls. No relinking. Not _nothing_. One
instruction, that's it.
See for example Uli's posting in this thread from the day before
yesterday, message ID <3DFF6D4B.3060107@redhat.com>. So please stop
arguing about any extra work, because none is needed.
Linus
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: H. Peter Anvin @ 2002-12-19 22:23 UTC (permalink / raw)
To: Pavel Machek
Cc: dean gaudet, Linus Torvalds, Dave Jones, Ingo Molnar,
linux-kernel
In-Reply-To: <20021219222136.GC17941@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
> Hi!
>
>
>>>>don't many of the multi-CPU problems with tsc go away because you've got a
>>>>per-cpu physical page for the vsyscall?
>>>>
>>>>i.e. per-cpu tsc epoch and scaling can be set on that page.
>>>
>>>Problem is that cpu's can randomly drift +/- 100 clocks or so... Not
>>>nice at all.
>>>
>>
>>?100 clocks is what... ?50 ns these days? You can't get that kind of
>>accuracy for anything outside the CPU core anyway...
>
> 50ns is bad enough when it makes your time go backwards.
>
Backwards?? Clock spreading should make the rate change, but it should
never decrement.
-hpa
^ permalink raw reply
* Weight in SAME and SNAT targets?
From: Peter Surda @ 2002-12-19 22:17 UTC (permalink / raw)
To: netfilter-devel
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hello dear developers!
According to the documentation, when doing SNAT to multiple IPs, it chooses
the IP with the lowest number of active connections. I assume SAME uses a
similar method as well.
I tried very hard to find the place in the code responsible for this, but
apparently I am blind or my grep is fscked. Could you please kindly direct me
to the file with the code and perhaps even some docs?
I currently use SNAT and SAME to loadbalance over several lines (don't explain
to me it shouldn't be done this way, our provider can't manage to persuade
their cisco to do "normal" loadbalancing so this is the only way that works).
However, soon we'll have lines with different bandwidth, and the current
method would cause suboptimal results (well, I can theoretically use more IPs
per line to do this, this possibility is being investigated). But this
wouldn't be necessary if it was possible to give the IPs different weight. I
don't think coding this is that difficult, but not being able to find the
responsible lines in code is a big showstopper.
Anyway, netfilter rocks, you can do a lot of cool stuff with it.
Bye,
Peter Surda (Shurdeek) <shurdeek@panorama.sth.ac.at>, ICQ 10236103, +436505122023
--
Press every key to continue.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
^ permalink raw reply
* Re: An array failover driver
From: Steven Dake @ 2002-12-19 22:17 UTC (permalink / raw)
To: Qi, Yanling; +Cc: 'linux-scsi-reflector'
In-Reply-To: <EB1DF7EA0D32D611B79C0002A51363F194A7BE@exw-ks.ks.lsil.com>
There is a failover driver as part of the MD driver system. I think
someone has worked on a SCSI multipathing driver that automatically
picks up redundant paths and fails over on retries, etc.
-steve
Qi, Yanling wrote:
>Hi All,
>
>I am going to develop a multiple-pathing driver to support our storage array
>hardware on Linux(2.4 and later). I prefer the driver sit on the top of HBA
>drivers (fibre channel adapter drivers) and below middle level (the unifying
>layer). In other words, insert my pseudo driver into middle level and lower
>level drivers. The driver will take care of path failover. I am still in
>research phase. Do you have any suggestions?
>
>
>Thanks,
>
>Yanling Qi
>-
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
^ permalink raw reply
* Bug? undefined reference to `input_event'
From: mdew @ 2002-12-19 22:22 UTC (permalink / raw)
To: Linux Kernel
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
in both the 2.5.52, and bitkeeper trees, i get this error with make
bzImage.
Generating include/linux/compile.h (updated)
gcc -Wp,-MD,init/.version.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=pentium3
-Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix
include -DKBUILD_BASENAME=version -DKBUILD_MODNAME=version -c -o
init/version.o init/version.c
ld -m elf_i386 -r -o init/built-in.o init/main.o init/version.o
init/do_mounts.o init/initramfs.o
ld -m elf_i386 -e stext -T arch/i386/vmlinux.lds.s
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/built-in.o
--start-group usr/built-in.o arch/i386/kernel/built-in.o
arch/i386/mm/built-in.o arch/i386/mach-generic/built-in.o
kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o
security/built-in.o crypto/built-in.o lib/lib.a arch/i386/lib/lib.a
drivers/built-in.o sound/built-in.o arch/i386/pci/built-in.o
net/built-in.o --end-group -o .tmp_vmlinux1
drivers/built-in.o(.text+0x2663f): In function `kd_nosound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x26664): In function `kd_nosound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x26729): In function `kd_mksound':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x27622): In function `kbd_bh':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x27641): In function `kbd_bh':
: undefined reference to `input_event'
drivers/built-in.o(.text+0x27660): more undefined references to
`input_event' follow
drivers/built-in.o(.text+0x27b64): In function `kbd_connect':
: undefined reference to `input_open_device'
drivers/built-in.o(.text+0x27b8f): In function `kbd_disconnect':
: undefined reference to `input_close_device'
drivers/built-in.o(.init.text+0x54f1): In function `kbd_init':
: undefined reference to `input_register_handler'
make: *** [.tmp_vmlinux1] Error 1
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 19344 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y
#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_NAMES=y
# CONFIG_PNP_CARD is not set
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_PNPBIOS=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_IDEDMA_FORCED=y
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_BLK_DEV_IDE_MODES=y
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_TOS is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_XFRM_USER is not set
#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IPV6 is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
# CONFIG_NET_CLS is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO_TUNE_TWISTER=y
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
CONFIG_SHAPER=m
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=m
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=m
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_INTEL_RNG=y
# CONFIG_AMD_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP3 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_AMD_8151 is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_SYSV_FS is not set
CONFIG_UDF_FS=y
# CONFIG_UFS_FS is not set
CONFIG_XFS_FS=y
CONFIG_XFS_RT=y
# CONFIG_XFS_QUOTA is not set
CONFIG_XFS_POSIX_ACL=y
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
CONFIG_CIFS=m
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_NCP_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_FS_MBCACHE=y
CONFIG_FS_POSIX_ACL=y
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
CONFIG_SOUND=y
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SND_YMFPCI=y
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set
#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_UHCI_HCD=y
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# SCSI support is needed for USB Storage
#
#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_TEST is not set
#
# Bluetooth support
#
# CONFIG_BT is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_KALLSYMS=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_X86_BIOS_REBOOT=y
^ permalink raw reply
* /proc/mounts and data=journal
From: Russell Coker @ 2002-12-19 22:16 UTC (permalink / raw)
To: ReiserFS
I've applied the patches for mounting with data=journal. However one problem
that I have discovered is that the data=journal status of a file system is
not shown in /proc/mounts, other tunable options of a file system such as
noatime are shown.
I think that this is a bug.
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Pavel Machek @ 2002-12-19 22:21 UTC (permalink / raw)
To: H. Peter Anvin
Cc: Pavel Machek, dean gaudet, Linus Torvalds, Dave Jones,
Ingo Molnar, linux-kernel
In-Reply-To: <3E0245C1.5060902@transmeta.com>
Hi!
> >>don't many of the multi-CPU problems with tsc go away because you've got a
> >>per-cpu physical page for the vsyscall?
> >>
> >>i.e. per-cpu tsc epoch and scaling can be set on that page.
> >
> > Problem is that cpu's can randomly drift +/- 100 clocks or so... Not
> > nice at all.
> >
>
> ?100 clocks is what... ?50 ns these days? You can't get that kind of
> accuracy for anything outside the CPU core anyway...
50ns is bad enough when it makes your time go backwards.
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: H. Peter Anvin @ 2002-12-19 22:18 UTC (permalink / raw)
To: Pavel Machek
Cc: dean gaudet, Linus Torvalds, Dave Jones, Ingo Molnar,
linux-kernel
In-Reply-To: <20021218235327.GC705@elf.ucw.cz>
Pavel Machek wrote:
>>
>>don't many of the multi-CPU problems with tsc go away because you've got a
>>per-cpu physical page for the vsyscall?
>>
>>i.e. per-cpu tsc epoch and scaling can be set on that page.
>
> Problem is that cpu's can randomly drift +/- 100 clocks or so... Not
> nice at all.
>
±100 clocks is what... ±50 ns these days? You can't get that kind of
accuracy for anything outside the CPU core anyway...
-hpa
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.