* Re: include order for i2c-amd8111
From: Pavel Machek @ 2003-01-08 12:06 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Rusty Russell, Pavel Machek, kernel list
In-Reply-To: <20030107114403.A5029@ucw.cz>
Hi!
> > > It seems all linux then all asm is prefered order...
> > > > > Yes, but not for any great reason, AFAICT. I think this comes under
> > the "too trivial" rule (ie. I'll accept it from the author, but not
> > someone else).
>
> The author (me ;) definitely doesn't mind you applying the patch, but
> would prefer if the one who pushed the 8111 driver into the kernel
> (Pavel) would update it to the version found in lm_sensors 2.7.0 at the
> same time.
Do you think you can mail me that file?
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Gabriel Paubert @ 2003-01-10 18:08 UTC (permalink / raw)
To: Linus Torvalds
Cc: Ingo Molnar, Jamie Lokier, Ulrich Drepper, davej, linux-kernel
Linus Torvalds wrote:
> It shouldn't matter.
>
> NT is only tested by "iret", and if somebody sets NT in user space they
> get exactly what they deserve.
Indeed. I realized after I sent the previous mail that I had missed the
flags save/restore in switch_to :-(
Still, does this mean that there is some micro optimization opportunity in
the lcall7/lcall27 handlers to remove the popfl? After all TF is now
handled by some magic in do_debug unless I miss (again) something,
NT has become irrelevant, and cld in SAVE_ALL takes care of DF.
In short something like the following (I just love patches which only
remove code):
===== entry.S 1.51 vs edited =====
--- 1.51/arch/i386/kernel/entry.S Mon Jan 6 04:54:58 2003
+++ edited/entry.S Fri Jan 10 18:57:42 2003
@@ -156,16 +156,6 @@
movl %edx,EIP(%ebp) # Now we move them to their "normal" places
movl %ecx,CS(%ebp) #
- #
- # Call gates don't clear TF and NT in eflags like
- # traps do, so we need to do it ourselves.
- # %eax already contains eflags (but it may have
- # DF set, clear that also)
- #
- andl $~(DF_MASK | TF_MASK | NT_MASK),%eax
- pushl %eax
- popfl
-
andl $-8192, %ebp # GET_THREAD_INFO
movl TI_EXEC_DOMAIN(%ebp), %edx # Get the execution domain
call *4(%edx) # Call the lcall7 handler for the domain
>>For example, set NT and then execute sysenter with garbage in %eax, the
>>kernel will try to return (-ENOSYS) with iret and kill the task. As long
>>as it only allows a task to kill itself, it's not a big deal. But NT is
>>not cleared across task switches unless I miss something, and that looks
>>very dangerous.
>
>
> It _is_ cleared by task-switching these days. Or rather, it's saved and
> restored, so the original NT setter will get it restored when resumed.
Yeah, sorry for the noise.
>
>
>>I'm no Ingo, unfortunately, but you'll need at least the following patch
>>(the second hunk is only a typo fix) to the iret exception recovery code,
>>which used push and pops to get the smallest possible code size.
>
>
> Good job.
That was too easy since I did originally suggest the push/pop sequence :-)
Gabriel.
^ permalink raw reply
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20
From: Anthony Lau @ 2003-01-10 18:09 UTC (permalink / raw)
To: William Lee Irwin III, linux-kernel
In-Reply-To: <20030110104827.GM23814@holomorphy.com>
On Fri, Jan 10, 2003 at 02:48:27AM -0800, William Lee Irwin III wrote:
Hello,
> On Fri, Jan 10, 2003 at 12:37:14AM -0800, Anthony Lau wrote:
> > 1.5GB physical RAM (MemTest86 run for 2 times, no errors)
> > 2.0GB VM on a partition
> > Aopen AX34u with Via Apollo Pro 133T chipset
>
> Hmm, I'd call the "VM on a partition" something like "swap" myself.
It was getting a bit late in the evening for me. =)
> Looks like someone e.g. invalidate_inode_pages(), truncate_inode_pages(),
> etc. etc., left pages hanging around. Borderline VM/vfs stuff. Or swap
> code mangled something important. This oops either has buttloads of
> stack noise or some other issue corrupting it. Can you find the first
> oops? If this is not the first oops, then it's probably not useful.
That was the first Oops message logged. System instability starts before
any oop messages begin to show up in the standard syslogd logs. Something
does appear in ksymoops. I have setup "klogd -x" and await the next log.
--
Anthony
^ permalink raw reply
* Re: NAT on the same ethernet card ?
From: Peter Surda @ 2003-01-10 17:55 UTC (permalink / raw)
To: netfilter-devel
In-Reply-To: <001801c2b8cd$fa819d00$7901000a@nivel5.cl>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
On Fri, Jan 10, 2003 at 02:30:32PM -0300, Miguel Angel Amador Lorca wrote:
> it' is possible that netfilter make NAT or MASQ over a tcp-packet from the
> one net (10.0.1.0) , and back to the same net (back to the 10.0.1.0 again )
> ?
Yes, by combining DNAT and SNAT. Next time post into -user mailing list, this
one is for development.
> Miguel Angel Amador Lorca | mailto:amador@puc.cl
Bye,
Peter Surda (Shurdeek) <shurdeek@panorama.sth.ac.at>, ICQ 10236103, +436505122023
--
If Bill Gates had a dime for every time a Windows box crashed...
...Oh, wait a minute, he already does.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
^ permalink raw reply
* Re: Kernel Oops with HIMEM+VM in 2.4.19,20
From: Anthony Lau @ 2003-01-10 18:02 UTC (permalink / raw)
To: Denis Vlasenko; +Cc: linux-kernel
In-Reply-To: <200301100908.h0A98ks15321@Port.imtp.ilyichevsk.odessa.ua>
On Fri, Jan 10, 2003 at 11:08:39AM +0200, Denis Vlasenko wrote:
> On 10 January 2003 10:37, Anthony Lau wrote:
> > Hello,
> >
[snip]
>
> You mean when your system starts to swap? Details?
> (How much/how heavy it swaps before oops? vmstat output?)
With very little swapping and <10MB of VM in use as reported by
the "free" command (Debian SID).
Next time I get an oops I will get the vmstat output.
[snip]
> Kernel version and .config?
> Arrange klogd to be started with -x. Process oopses with ksymoops.
I have tried vanilla 2.4.19+HTB2 patch and vanilla 2.4.20.
I have setup klogd with -x now and await the next oops.
Thanks for the list of VM people. They were not obviously listed
in the MAINTAINER file that came with the kernel sources.
--
Anthony
^ permalink raw reply
* Re: How build dependencies work/are supposed to work in 2.5
From: Petr Vandrovec @ 2003-01-10 18:03 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: linux-kernel
On 10 Jan 03 at 18:35, Sam Ravnborg wrote:
> On Thu, Jan 09, 2003 at 11:33:32PM +0100, Petr Vandrovec wrote:
> > So I'd like to ask whether current kernel build system is supposed
> > to track changes in include files automagically, or whether I'm supposed
> > to run 'make dep' from time to time?
>
> Until now I'm only aware of one set of problems that kbuild does not
> handle correct. That is when the timestamp of the files goes backward.
> This happens at least in the following situations:
> 1) A file is saved, and mv is used to restore the original
> 2) CVS is configured to preserve original timestamp when files are 'dumped'
> 3) NFS mounted filesystems where the clock is wrong. Timezone
> inconsistency for eaxmple.
>
> I assume you were hit by some flavour of 1) ???
Thanks for your explanation. After I was thinking about it, you are
probably right. Maybe that I just copied console_struct.h from
distribution kernel instead of reverting patch to get to the original
version, and I forgot touching file.
Sorry for confusion.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
^ permalink raw reply
* [ANNOUNCE] LTP-20030110
From: Jeff Martin @ 2003-01-10 18:00 UTC (permalink / raw)
To: linux-kernel
The Linux Test Project test suite LTP-20030110.tgz has been released.
Visit our website (http://ltp.sourceforge.net) to download the latest
version of the testsuite, and for information on test results on
pre-releases, release candidates & stable releases of the kernel. There
is also a list of test cases that are expected to fail, please find
the list at (http://ltp.sourceforge.net/expected-errors.php)
The highlights of this release are:
- Many new tests from Wipro.
- Many new SPIE tests ported.
- More than 40 new tests.
- LTP now has over 900 tests.
- Many bug-fixes
We encourage the community to post results, patches, or new tests on our
mailing list, and to use the CVS bug tracking facility to report
problems that you might encounter. More details available at our
web-site.
ChangeLog
----------
- Added New test case to test 'file' command. ( Manoj Iyer )
- Added new test to test basic functionality of ( Manoj Iyer )
CRONTAB, CRON etc.
- Added new test case to test eject command ( Manoj Iyer )
- Added new tests to test logrotate ( Manoj Iyer )
- Added new testcase to test basic functionality ( Manoj Iyer )
of tar command.
- Fixed mem01: The free memory size was being ( Robbie Williamson )
incorrectly calculated, plus it could not
handle large amounts of memory...now using
long int, instead of int.
- Fixed mem01: Test was not cleaning up correctly ( Robbie Williamson )
after a failure.
- Initial checkin of shmt, shared memory tests ( Robbie Williamson )
from SPIE suite
- Initial checkin of pty testcases: hangup01(), ( Robbie Williamson )
ptem01() and pty01() from SPIE testsuite.
- Added code to abort01.c to use the ( Robbie Williamson )
tst_tmpdir()/tst_rmdir() APIs
- Added ported abort() test ( Ananda Venkataraman)
- Added adjtimex() tests ( Saji Kumar )
- Added capget() tests ( Saji Kumar )
- Added capset() tests ( Saji Kumar )
- Added ported test, creat08 ( Airong Zhang )
- create08 was initially ported to create users ( Robbie Williamson )
and groups that it needed. Rewrote the test to
use existing users/groups that are checked for
when the LTP is installed.
- Applied patch to create_module02 from creator ( T.L.Madhu )
- Applied patch to delete_module02 from creator ( T.L.Madhu )
- Added code to delete_module03 to allow tests to ( Robbie Williamson )
execute under pan.
- Applied patch to delete_module03 from creator ( T.L.Madhu )
- Added ported dup06 and dup07 tests ( Airong Zhang )
- Added ported dup202 and dup205 tests ( Airong Zhang )
and cleaned up some other files
- Initial checkin of fdatasync() tests ( T.L. Madhu )
- Added new flock04 and flock05 tests ( Vatsal Avasthi )
- Added ported fmtmsg() test ( Ananda Venkataraman)
- Added functional test to gethostid01 to compare ( Paul Larson )
result from gethostid() versus the hostid
command
- Initial checkin of getrusage() tests ( Saji Kumar )
- Added ioperm() tests ( Subhabrata Biswas )
- Added iopl() tests ( Subhab Biswas )
- Added ported kill() tests ( Ananda Venkataraman)
- Added ported mallopt() test ( Ananda Venkataraman)
- Added ported memcmp() test ( Ananda Venkataraman)
- Added ported memcpy() test ( Ananda Venkataraman)
- Added ported memset() test ( Ananda Venkataraman)
- Fixed mkdir09: the getopts() call was returning ( Robbie Williamson )
it's -1 to a char variable. This was incorrect
and causing the test to loop forever on certain
architectures.
- Initial checkin of munlockall() tests ( Sowmya Adiga )
- Fixed nftw64: tst_rmdir was in the wrong ( Robbie Williamson )
location.
- Added ported open09() test ( Airong Zhang )
- Initial checkin of prctl() tests ( Saji Kumar )
- Added ported profil() test ( Ananda Venkataraman)
- Initial checkin of ptrace() tests ( Saji Kumar )
- Added code to query_module tests to allow ( Robbie Williamson )
execution under pan.
- Initial checkin of reboot() tests ( Aniruddha Marathe )
- Initial checkin of sched_rr_get_interval tests ( Saji Kumar )
- Added setresgid() tests ( T.L. Madhu )
- Fixed setrlimit03 to work on 2.5 and cleanup ( Paul Larson )
- Added socketcall() tests ( Adiga Sowmya )
- Added ported string.h test string01 ( Ananda Venkataraman)
- Added swapoff() tests ( Aniruddha Marathe )
- Added swapoff() tests ( Aniruddha Marathe )
- Added swapon() test ( Aniruddha Marathe )
- Made corrections to swapon02 to make sure the ( Robbie Williamson )
child exits.
- Added ported syscall() test ( Ananda Venkataraman)
- Removed an erroneous testcase in sysconf01 and ( Robbie Williamson )
corrected a typo issue.
- Initial checkin of sysfs() tests ( Aniruddha Marathe )
- Made changes to allow the syslog tests to ( Robbie Williamson )
execute in pan and corrected a bug in backup
code for syslog.conf original file.
- Added syslog11 & syslog12 tests ( T.L. Madhu )
- Fixed syslogtst if-statement comparing a file ( Robbie Williamson )
descriptor to a hardcoded number was changed to
allow the test to run under pan.
- Changed the file opened for the 6th case in ( Robbie Williamson )
syslogtst.
- Added ported abs() test ( Ananda Venkataraman)
- Added ported atof() test ( Ananda Venkataraman)
- Added ported nextafter() test ( Ananda Venkataraman)
- Corrected bug in cleanup section of fsx.sh ( Robbie Williamson )
- Added code to rusers01 to change a FQDN in ( Robbie Williamson )
RHOST to short name.
- Fixed testsf_c bug in char* not large enough to ( Robbie Williamson )
hold argv[4] string.
- Added command line version of LTP harness APIs ( Manoj Iyer )
these commands will print LTP test results in
LTP harness format just like the ones printed
by C testcases. These commands can be used in
shell scripts and other non-C testcases.
- Added load generator tool, stress ( Amos Waterland )
- Modified runalltests.sh to print default ( Manoj Iyer )
settings
- Modified runalltests.sh to run LTP under stress ( Manoj Iyer )
Jeff Martin (ffej_AT_us.ibm.com)
Linux Test Project
IBM Linux Technology Center
^ permalink raw reply
* set_user_nice() not defined on 2.4.21+
From: Xiaogeng (Shawn) Jin @ 2003-01-10 18:21 UTC (permalink / raw)
To: linux-mtd
Hi,
When compiled JFFS2 with kernel 2.4.21-pre3, the linker complains that
the reference to set_user_nice() in function
jffs2_garbage_collect_thread() hasn't been defined. I traced the code
down to <linux/mtd/compatmac.h> and found that set_user_nice() is not
defined if linux verion is equal or greater than 2.4.21. See the code
below. Why? Does it mean that 2.4.21+ has already such a function
defined somewhere else or that 2.4.21+ doesn't need it? Actually I
searched 2.4.21-pre3 code and found no set_user_nice() defined except in
<linux/mtd/compatmac.h>. I guess it's possibly a bug.
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,4,0) /* Is this right? */
#define set_user_nice(tsk, n) do { (tsk)->priority = 20-(n); } while(0)
#elif LINUX_VERSION_CODE < KERNEL_VERSION(2,4,21) &&
!defined(RED_HAT_LINUX_KERNEL)
#define set_user_nice(tsk, n) do { (tsk)->nice = n; } while(0)
#endif
--
Shawn Jin
RedSwitch Inc.
^ permalink raw reply
* RE: [PATCH] [2.5] IRQ distribution in the 2.5.52 kernel
From: Kamble, Nitin A @ 2003-01-10 17:59 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel, Saxena, Sunil, Mallick, Asit K, Nakajima, Jun
Thanks for the comment. I will take it out.
Nitin
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Tuesday, January 07, 2003 9:12 PM
> To: Kamble, Nitin A
> Cc: linux-kernel@vger.kernel.org; Saxena, Sunil; Mallick, Asit K;
> Nakajima, Jun
> Subject: Re: [PATCH] [2.5] IRQ distribution in the 2.5.52 kernel
>
> On Tue, Jan 07, 2003 at 06:52:59PM -0800, Kamble, Nitin A wrote:
> > +# define MIN(a,b) (((a) < (b)) ? (a) : (b))
> > +# define MAX(a,b) (((a) > (b)) ? (a) : (b))
>
> There are alread definitions for min() and max(), it would be good to
> use them and not try to define your own.
>
> thanks,
>
> greg k-h
^ permalink raw reply
* Re: [BENCHMARK] 2.5.53 with contest
From: Rob Landley @ 2003-01-10 17:54 UTC (permalink / raw)
To: Con Kolivas, linux kernel mailing list
In-Reply-To: <200301090732.24440.conman@kolivas.net>
On Wednesday 08 January 2003 20:32, Con Kolivas wrote:
> > Could you add a time per load metric? (I.E. 86.9/21=4.14 seconds. Yeah,
> > I could do the math myself, but that and total time are usually what I'm
> > trying to compare when I look at these. Maybe it's just me...)
>
> If you look at the information carefully the meaningful number is
>
> (Loads ) / ( process_load_time - no_load_time)
Hmmm... Have to think about this a sec...
So far I've just been looking at the deltas between versions, like I said,
with the implicit assumption that no_load_time remains roughly constant
(after all, kernel build time is what everybody's been optimizing for since
the 2.0 era).
There are really two things it would be nice to isolate: one is the amount of
thrashing the extra processing introduces, slowing down the whole system.
The other is the balancing decisions that are made (the amount of work done
by io_load or mem_load varies and has no impact on the termination of the
test as a whole...) I sort of want to isolate out the balancing decisions a
bit, or at least have a metric to look at them and compare them. (I.E. "yeah
it got slower, but it did more work overall". Now is this what everybody
WANTS, and could we maybe twiddle this with precedence in the scheduler or
something if it isn't?)
I suppose your metric is a more accurate way of measuring that. Cool.
> but keep an eye out for a new version soon.
>
> Con
Of course, :)
Rob
--
penguicon.sf.net - A combination Linux Expo and Science Fiction Convention
with GOHs Terry Pratchett, Eric Raymond, Pete Abrams, Illiad & CmdrTaco.
^ permalink raw reply
* RE: sd_read_cache_type
From: Cress, Andrew R @ 2003-01-10 17:35 UTC (permalink / raw)
To: 'James Bottomley', Andries.Brouwer
Cc: linux-kernel, linux-scsi, linux-usb-devel
RE: cache
Yes, at least a synchronize, but can we always know (in time) if the medium
has been removed? We may not always get an eject request, right?
I think write-back cache is inherently unsafe in general, but I guess we
have to allow unsafe things like that for non-production use.
Andy
-----Original Message-----
From: James Bottomley
Sent: Friday, January 10, 2003 10:14 AM
[...]
Well, the cache is pretty often part of the permanent assembly, not part of
the removable medium, so I think it should still be called for removable
media. That begs the question, of course, what should the cache type be---it
strikes me as rather unsafe to have a removable RW medium with a write back
cache? I suppose at the very least we should to a SYNCHRONIZE on ejection
if
it's write back?
James
[...]
^ permalink raw reply
* Linux 2.4.21-pre3-ac3
From: Alan Cox @ 2003-01-10 17:49 UTC (permalink / raw)
To: linux-kernel
Handle with care, this should work nicely but does have more minor IDE
changes paticularly relevant to laptop IDE suspend/resume.
Linux 2.4.21pre3-ac3
o Address comments on wcache value/issuing (me)
cache flush requests
o Update credits entry for Stelian Pop (Stelian Pop)
o Backport some sonypi improvements from 2.5 (Kunihiko IMAI)
o Fix pdcraid/silraid symbol clash (Arjan van de Ven)
o Fix ehci build with older gcc (Greg Kroah-Hartmann)
o Fix via 8233/5 hang (me)
o Fix non SMP cpufreq build (Eyal Lebidinsky)
o Fix sbp2 build with some config options (Eyal Lebidinsky)
o Fix compile in kernel for Aurora SIO16 (Adrian Bunk)
o Fix ATM build bugs (Francois Romieu)
o Fix an ipc/sem.c race (Bernhard Kaindl)
o Fix toshiba keyboard double release (Unknown)
o CPUFreq updaes/fixes (Dominik Brodowski)
o Natsemi Geode/Cyrix MediaGX cpufreq support (Dominik Brodowski)
o Add frequency table helpers to CPUfreq (Dominik Brodowski)
Linux 2.4.21pre3-ac2
o Fix the dumb bug in skb_pad (Dave Miller)
o Confirm some sparc bits are wrong and drop them (Dave Miller)
o Remove a wrong additional copyright comment (Dave Miller)
o Upgrade IPMI driver to v16 (Corey Minyard)
o Fix 3c523 compile (Francois Romieu)
o Handle newer rpm where -ta is rpmbuild not rpm (me)
o Driver for Aurora Sio16 PCI adapter series (Joachim Martillo)
(SIO8000P, 16000P, and CPCI)
| Initial merge
o Backport Hammer 32bit mtrr/nmi changes (Andi Kleen)
o Add the fast IRQ path to via 8233/5 audio (me)
Linux 2.4.21pre3-ac1
+ Handle battery quirk on the Vaio Z600-RE (Paul Mitcheson)
* EHCI USB updates (David Brownell)
+ IDE Raid support for AMI/SI 'Medley' IDE Raid (Arjan van de Ven)
+ NVIDIA nForce2 IDE PCI identifiers (Johannes Deisenhofer,
Tim Krieglstein)
* CPU bitmask truncation fix (Bjorn Helgaas)
o HP100 cleanup (Pavel Machek)
o Fix initial capslock handling on USB keyboard (Pete Zaitcev)
+ Update dscc4 driver for new wan (Francois Romieu)
+ Fix boot on Chaintech 4BEA/4BEA-R and (Alexander Achenbach)
Gigabyte 9EJL by handing wacky E820 memory
reporting
o SysKonnect driver updates (Mirko Lindner)
o Fix memory leak in n_hdlc (Paul Fulghum)
o Fix missing mtd dependancy (Herbert Xu)
+ Clean up ide-tape printk stuff (Pete Zaitcev)
+ IDE tape fixes (Pete Zaitcev)
o Fix size reporting of large disks in scsi (Andries Brouwer)
+ Fix excessive stack usage in NMI handlers (Mikael Pettersson)
+ Add support for Epson 785EPX USB printer pcmcia (Khalid Aziz)
* Quirk handler to sort out IDE compatibility (Ivan Kokshaysky)
mishandling
+ Model 1 is valid for PIV in MP table (Egenera)
+ Ethernet padding fixes for various drivers (me)
o Allow trident codec setup to time out (Ian Soboroff)
This can happen with non PM codecs
o Fix broken documentation link (Henning Meier-Geinitz)
o Update video4linux docbook (William Stimson)
o Correct kmalloc check in dpt_i2o (Pablo Menichini)
o Shrink kmap area to required space only (Manfred Spraul)
o Fix irq balancing (Ben LaHaise)
o CPUfreq updates (Dominik Brodowski)
o Fix typo in pmagb fb (John Bradford)
o EDD backport (Matt Domsch)
REMOVED FOR NOW
- RMAP
REMOVED FOR GOOD
- LLC (See 2.5)
- VaryIO (Never accepted mainstream)
^ permalink raw reply
* [U-Boot-Users] PPCBoot vxworks question
From: Timothy Canham @ 2003-01-10 17:40 UTC (permalink / raw)
To: u-boot
I am new to the list and new to PPCBoot/UBoot, so apologies in advance
if this is old territory. I am trying to load a vxworks kernel located
on an external server, using the typical vxworks boot loader. i.e., the
vxworks boot loader loads a kernel from a remote server using rsh and
jumps to it. From what I can see, PPCBoot has the bootvx command, but it
appears to require that the vxworks kernel already be loaded to work.
Can someone post the equivalent procedure to duplicate in PPCBoot what
the vxworks boot loader does?
--
-------
Timothy K. Canham
Isaiah 26:3
tim at timcanham.com
http://www.timcanham.com
^ permalink raw reply
* RE: sd_read_cache_type
From: Cress, Andrew R @ 2003-01-10 17:35 UTC (permalink / raw)
To: 'James Bottomley', Andries.Brouwer
Cc: linux-kernel, linux-scsi, linux-usb-devel
RE: cache
Yes, at least a synchronize, but can we always know (in time) if the medium
has been removed? We may not always get an eject request, right?
I think write-back cache is inherently unsafe in general, but I guess we
have to allow unsafe things like that for non-production use.
Andy
-----Original Message-----
From: James Bottomley
Sent: Friday, January 10, 2003 10:14 AM
[...]
Well, the cache is pretty often part of the permanent assembly, not part of
the removable medium, so I think it should still be called for removable
media. That begs the question, of course, what should the cache type be---it
strikes me as rather unsafe to have a removable RW medium with a write back
cache? I suppose at the very least we should to a SYNCHRONIZE on ejection
if
it's write back?
James
[...]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
^ permalink raw reply
* Re: Re: NFS as a Cluster File System.
From: Greg Lindahl @ 2003-01-10 17:38 UTC (permalink / raw)
To: Trond Myklebust; +Cc: nfs, linux-ha
In-Reply-To: <shs3co1kq1e.fsf@charged.uio.no>
> > I think this can be resolved with the "noac" mount option
> > (prior to V4).
>
> Nope. It can only be resolved using file locking.
There are 2 consistency problems: metadata and data.
Metadata is solved by noac. And yes, some MPI programs do things like
"node 0 writes out a bunch of files, then tells all the other nodes to
read one file each." This means that you have about 1/100 of a second
window between creation on one client and reading on a different client.
Data consistency is solved by file locking.
-- greg
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply
* Re: any chance of 2.6.0-test*?
From: Linus Torvalds @ 2003-01-10 17:38 UTC (permalink / raw)
To: Jochen Friedrich
Cc: Alan Cox, William Lee Irwin III, Linux Kernel Mailing List
In-Reply-To: <Pine.LNX.4.44.0301101833220.1492-100000@gfrw1044.bocc.de>
On Fri, 10 Jan 2003, Jochen Friedrich wrote:
>
> Full ACK. There are still archs without working module code, right now
> (parisc and mips come to my mind).
Note that other architectures have never been an issue for releasing new
kernels, and that is _particularly_ true of architectures like parisc and
mips that haven't even _tried_ to track development kernels. In fact, mips
"anti-maintenance" has often actively discouraged people from even
bothering to update mips code when adding new features.
Linus
^ permalink raw reply
* Re: [TRIVIAL] [PATCH 1 of 3] Fix errors making Docbook documentation
From: Sam Ravnborg @ 2003-01-10 17:40 UTC (permalink / raw)
To: Rusty Russell, Alan Cox
Cc: Alan Cox, Linus Torvalds, Linux Kernel Mailing List, Craig Wilkie
In-Reply-To: <20030110073328.A11712C0DD@lists.samba.org>
> >
> > Grab the docbook for those files from 2.4 and also the changes to the
> > docbook generator
I have updated scripts/kernel-doc once from 2.4, I will check again
if there are new updates.
I saw good improvements in reporting when updating it last time,
people actually had a chance to locate were documentation was missing.
And I prefer a warning, to remind people that an update is needed.
Sam
^ permalink raw reply
* Re: BLKBSZSET still not working on 2.4.18 ?
From: Andries Brouwer @ 2003-01-10 17:40 UTC (permalink / raw)
To: Alan Cox; +Cc: John Bradford, ludovic.drolez, Linux Kernel Mailing List
In-Reply-To: <1042222490.32175.5.camel@irongate.swansea.linux.org.uk>
On Fri, Jan 10, 2003 at 06:14:51PM +0000, Alan Cox wrote:
> On Fri, 2003-01-10 at 17:08, John Bradford wrote:
> > Didn't some really obscure IBM drives use it for something internally,
> > and shortly after everybody else had to stop using it incase they
> > overwrote the custom data at the end of an IBM disk, or am I thinking
> > of something else?
> Something else - EFI uses the last sector for partitioning as one example.
> Drives do have protected private areas but they are shielded from normal
> use for obvious reasons
There is also a much older matter. In the distant past IBM used the
last cylinder for testing. That means that many FDISK versions and many
BIOSes subtract one from the number of available cylinders.
There are several ways to ask the BIOS for the size of a disk,
and some of these calls may invoke others, and then subtract one.
I have seen disks that had lost three cylinders that way.
Andries
^ permalink raw reply
* NAT on the same ethernet card ?
From: Miguel Angel Amador Lorca @ 2003-01-10 17:30 UTC (permalink / raw)
To: netfilter-devel
In-Reply-To: <20030110140544.GV1353@sunbeam.de.gnumonks.org>
it' is possible that netfilter make NAT or MASQ over a tcp-packet from the
one net (10.0.1.0) , and back to the same net (back to the 10.0.1.0 again )
?
____________
My PC---->tcp request ---> eth0 --> | |
(10.0.1.105) | FW |-
eth1 -----------> - internet
MyWWW <--eth0------ |___________
-mydns
(10.0.1.100)
Miguel Angel Amador Lorca | mailto:amador@puc.cl
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM d- s:+ a- C++++ UL+++ P- L+++ E--- W+++ N++ o K- w++
O- M- V- PS+ PE++ Y PGP- t 5 X+++ R !tv b+ DI- D
G++ e- h* r- y*
------END GEEK CODE BLOCK------
^ permalink raw reply
* Re: any chance of 2.6.0-test*?
From: Jochen Friedrich @ 2003-01-10 17:37 UTC (permalink / raw)
To: Alan Cox; +Cc: William Lee Irwin III, Linus Torvalds, Linux Kernel Mailing List
In-Reply-To: <1042219147.31848.65.camel@irongate.swansea.linux.org.uk>
On 10 Jan 2003, Alan Cox wrote:
> On Fri, 2003-01-10 at 16:10, William Lee Irwin III wrote:
> > Any specific concerns/issues/wishlist items you want taken care of
> > before doing it or is it a "generalized comfort level" kind of thing?
> > Let me know, I'd be much obliged for specific directions to move in.
>
> IDE is all broken still and will take at least another three months to
> fix - before we get to 'improve'.
As is the whole frame buffer mess. USB slowly seems to return to a working
state. ISDN seems to be a total mess, as well.
> No more "ISAPnP TNG" and module rewrites please
Full ACK. There are still archs without working module code, right now
(parisc and mips come to my mind).
--jochen
^ permalink raw reply
* Re: How build dependencies work/are supposed to work in 2.5.5x
From: Sam Ravnborg @ 2003-01-10 17:35 UTC (permalink / raw)
To: Petr Vandrovec; +Cc: linux-kernel
In-Reply-To: <CC66A71361E@vcnet.vc.cvut.cz>
On Thu, Jan 09, 2003 at 11:33:32PM +0100, Petr Vandrovec wrote:
> So I'd like to ask whether current kernel build system is supposed
> to track changes in include files automagically, or whether I'm supposed
> to run 'make dep' from time to time?
Hi Petr,
First of all:
1) kbuild track changes in referenced include files
2) kbuild track changes in relevant CONFIG options
2) is done using the executable split-include.
When run split-include creates a tree of files in:
include/config/*
CONFIG_SND_PCM_OSS creates a file named include/config/snd/pcm, with the
name oss.h. oss.h contains
#define CONFIG_SND_PCM_OSS 1
split-include uses this to determine if the config option in question
has changed such that only files containing changes are touched.
split-include is run when include/linux/autoconf.h has changed.
And autoconf.h has .config as the prerequisite, so each time the
configuration has changed autoconf.h is generated, and all relevant
files in include/config/* is updated.
1) When a .c/.S file is compiled the option
-Wp,-MD,arch/i386/kernel/.mpparse.o.d
is used to generate a file containing dependencies as gcc sees it.
Now the binary fixdep is used to generate dependencies including references
to all include/config/* files corresponding to all cONfig options used
in a given file.
Try to view a .*.o.cmd file in kernel/ ar similar.
Until now I'm only aware of one set of problems that kbuild does not
handle correct. That is when the timestamp of the files goes backward.
This happens at least in the following situations:
1) A file is saved, and mv is used to restore the original
2) CVS is configured to preserve original timestamp when files are 'dumped'
3) NFS mounted filesystems where the clock is wrong. Timezone
inconsistency for eaxmple.
I assume you were hit by some flavour of 1) ???
kbuild-2.5 by Keith Ownes included timestamp checks, so that would have
catched the three cases described above.
I do not see any clean way to introduce this in existing kbuild,
and neither do i see a big need for it.
Anyway this belongs to the make problem domain - not kbuild core.
Sam
^ permalink raw reply
* Re: any chance of 2.6.0-test*?
From: Linus Torvalds @ 2003-01-10 17:29 UTC (permalink / raw)
To: Dave Jones; +Cc: Alan Cox, William Lee Irwin III, Linux Kernel Mailing List
In-Reply-To: <20030110170625.GE23375@codemonkey.org.uk>
On Fri, 10 Jan 2003, Dave Jones wrote:
>
> What's happening with the OSS drivers ?
> I'm still carrying a few hundred KB of changes from 2.4 for those.
> I'm not going to spent a day splitting them up, commenting them and pushing
> to Linus if we're going to be dropping various drivers.
I consider them to be old drivers, the same way "hd.c" was. Not
necessarily useful for most people, but neither was hd.c. And it was
around for a _long_ time (heh. I needed to check. The config option is
still there ;)
So I don't see a huge reason to remove them from the sources, but we might
well make them harder to select by mistake, for example. Right now the
config help files aren't exactly helpful, and the OSS choice is before the
ALSA one, which looks wrong.
They should probably be marked deprecated, and if they don't get a lot of
maintenance, that's fine.
Linus
^ permalink raw reply
* Re: [PATCH]Re: spin_locks without smp.
From: Alan Cox @ 2003-01-10 18:18 UTC (permalink / raw)
To: Manfred Spraul
Cc: Linux Kernel Mailing List, Maciej Soltysiak,
William Lee Irwin III
In-Reply-To: <3E1F00BB.2090904@colorfullife.com>
On Fri, 2003-01-10 at 17:19, Manfred Spraul wrote:
>
> disable_irq();
> spin_lock(&np->lock);
>
> That's what 8390.c uses, no need for an #ifdef.
Does someone have a card they can test that on. If so then I agree
entirely it is the best way to go
^ permalink raw reply
* Re: Re: NFS as a Cluster File System.
From: Lorn Kay @ 2003-01-10 17:19 UTC (permalink / raw)
To: trond.myklebust; +Cc: alanr, nfs, linux-ha
>
> >> NFS V3 and before have problems with "cache coherency". That
> >> is, the different nodes in the cluster are not guaranteed to
> >> see the same contents.
>
> > I think this can be resolved with the "noac" mount option
> > (prior to V4).
>
>Nope. It can only be resolved using file locking.
>
>Cheers,
> Trond
>
Meaning if you don't lock a file and just read it you may not see the what
another client has written to it, or is that not an issue because the other
client will have locked and then unlocked the file when it is done making
changes?
Thanks,
--K
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply
* Re: any chance of 2.6.0-test*?
From: Alan Cox @ 2003-01-10 18:16 UTC (permalink / raw)
To: Dave Jones
Cc: William Lee Irwin III, Linus Torvalds, Linux Kernel Mailing List
In-Reply-To: <20030110170625.GE23375@codemonkey.org.uk>
On Fri, 2003-01-10 at 17:06, Dave Jones wrote:
> What's happening with the OSS drivers ?
> I'm still carrying a few hundred KB of changes from 2.4 for those.
> I'm not going to spent a day splitting them up, commenting them and pushing
> to Linus if we're going to be dropping various drivers.
I'd hope they would go away but it seems that will be post 2.6. The
drivers do seem to mostly work in 2.5.x. I'm meaning the stuff that
doesn't compile and nobody gives a damn about.
^ 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.