Re: CLOCAL and TIOCMIWAIT

2001-02-27 Thread Theodore Y. Ts'o
Date:Mon, 26 Feb 2001 22:19:20 -0500 From: Jeremy Jackson <[EMAIL PROTECTED]> I had written a simple program 10-20 lines C to count pulses at rate of 1 per second give or take. It turned out that the driver disabled the UART's generation of interrupts completely for certai

Re: [CFT][RFC] ext2_new_inode() fixes and cleanup

2000-11-30 Thread Theodore Y. Ts&#x27;o
Date: Thu, 30 Nov 2000 17:13:27 -0500 (EST) From: Alexander Viro <[EMAIL PROTECTED]> * search for appropriate cylinder group had been taken out of the ext2_new_inode() into helper functions - find_cg_dir(sb, parent_group) and find_cg_other(sb, parent_group). Bug caught by D

Re: /dev/random probs in 2.4test(12-pre3)

2000-12-02 Thread Theodore Y. Ts&#x27;o
From: "Albert D. Cahalan" <[EMAIL PROTECTED]> Date:Sat, 2 Dec 2000 17:00:32 -0500 (EST) > Any programmer who has evolved sufficiently from a scriptie > should take necessary precautions to check how much data was > transferred. Those who don't..well, there is still tomorro

Re: Fasttrak100 questions...

2000-12-02 Thread Theodore Y. Ts&#x27;o
Date:Sat, 2 Dec 2000 17:18:43 + (GMT) From: Alan Cox <[EMAIL PROTECTED]> > This is currently happening with lucent winmodem driver: there's > modified version of serial.c, and customers are asked to compile it > and (staticaly-)link it against proprietary code to get us

Re: /dev/random probs in 2.4test(12-pre3)

2000-12-02 Thread Theodore Y. Ts&#x27;o
Date: Sat, 2 Dec 2000 18:34:44 -0500 (EST) From: Alexander Viro <[EMAIL PROTECTED]> Erm... Not that ignoring the return values was a bright idea, but the lack of reliable ordered datagram protocol in IP family is not a good thing. It can be implemented over TCP, but it's a big over

Re: Fasttrak100 questions...

2000-12-02 Thread Theodore Y. Ts&#x27;o
Date: Sat, 2 Dec 2000 18:21:26 -0700 From: "Jeff V. Merkey" <[EMAIL PROTECTED]> Under this argument, it is argued that the engineer who had source code access "inevitably used" negative knowledge he gained from his study of the Linux sources. Absent the vague descriptions of

Re: lost dirs after fsck-1.18 (kt133, ide, dma, test10, test11)

2000-12-03 Thread Theodore Y. Ts&#x27;o
From: "Saber Taylor" <[EMAIL PROTECTED]> Date:Sun, 03 Dec 2000 05:59:47 - Well that's the last time I run a devel kernel with a nontest system. sigh. Had one directory replaced with a different directory and also a directory replaced with a file. Possible further

Re: Small bugfix in ext2/namei.c

2000-09-01 Thread Theodore Y. Ts&#x27;o
Date:Fri, 1 Sep 2000 12:47:44 +0200 (MESZ) From: "Dr. Michael Weller" <[EMAIL PROTECTED]> Sorry, I've no idea about the ext2 and fs implementation. However did you read the comment below and convince yourself that 'err' is always set correctly? I looked at it and was convi

Re: Serial driver - overrun possible to overrun flip buffer? (2.4.0-test7)

2000-09-01 Thread Theodore Y. Ts&#x27;o
From: Russell King <[EMAIL PROTECTED]> Date: Fri, 1 Sep 2000 16:23:39 +0100 (BST) At the marked line (! - line 647), what if flip.count is equal to TTY_FLIPBUF_SIZE? Surely we're writing to a character outside the flag_buf_ptr array? If that is the case, should we not move this

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Theodore Y. Ts&#x27;o
From: Daniel Phillips <[EMAIL PROTECTED]> Date:Fri, 01 Sep 2000 20:49:14 +0200 Curiously, this field is measured in 512 byte units, giving a 2TB Ext2 filesize limit. That's starting to look uncomfortably small - I can easily imagine a single database file wanting to be big

Re: [OT] Re: Press release - here we go again!

2000-09-01 Thread Theodore Y. Ts&#x27;o
Date:Fri, 01 Sep 2000 08:47:04 -0700 From: Stephen Satchell <[EMAIL PROTECTED]> 5) Even better would be to obtain the services of a PR firm used to dealing with high-tech questions -- if you would like a list of potential sponsors I can poll the IPG to see who might be l

Re: thread group comments

2000-09-01 Thread Theodore Y. Ts&#x27;o
From: Ulrich Drepper <[EMAIL PROTECTED]> Date:01 Sep 2000 14:52:28 -0700 1st Problem: One signal handler process process-wide What is handled correctly now is sending signals to the group. Also that every thread has its mask. But there must be exactly one signal han

Re: [ANNOUNCE] Withdrawl of Open Source NDS Project/NTFS/M2FS forLinux

2000-09-03 Thread Theodore Y. Ts&#x27;o
Andre wrote: > Linux rejected the code because it does not understand nor does anyone > have the desire to learn what it does. Since it is not in the kernel > there is no GPL issue. Upon Microsoft's adpotion of the model they will That's B.S. The GPL is a Copyright license; it applies whether

Re: 2.4.0-test7 stallion.c is in the wrong directory.

2000-09-04 Thread Theodore Y. Ts&#x27;o
From: Russell Coker <[EMAIL PROTECTED]> Date:Mon, 4 Sep 2000 15:42:57 +0200 In test7 the stallion.c serial driver is in the drivers/media/video directory. This means that it won't compile and that compilation will break if the Stallion driver is enabled. Could this fil

Can someone send me a copy of the 0.0.9 cuecat kernel driver

2000-09-05 Thread Theodore Y. Ts&#x27;o
Did someone manage to get a copy of the 0.0.9 cuecat kernel driver before Lineo took it off the net (due to their getting threatenedd by Digital Convergence over some bogus "the driver has our intellectual property" threat)? If so, could someone send me a copy of the driver via e-mail? Thanks!!

Re: [ANNOUNCE] Withdrawl of Open Source NDS Project/NTFS/M2FS forLinux

2000-09-05 Thread Theodore Y. Ts&#x27;o
Date:Wed, 6 Sep 2000 01:43:47 +0100 (BST) From: Alex Buell <[EMAIL PROTECTED]> > Only, with the former, I get to restart the application everytime it > croaks, with the latter (modules excluded) I have to reboot. This is > much more time consuming and means you really have

Re: Availability of kdb

2000-09-11 Thread Theodore Y. Ts&#x27;o
Date:Sun, 10 Sep 2000 17:06:17 -0600 From: "Jeff V. Merkey" <[EMAIL PROTECTED]> One of the principal architects at Compaq called me Friday after reading Linus' email about not caring about commercial or support issues for commercialization of Linux on this topic-- his right

Re: Using Yarrow in /dev/random

2000-09-12 Thread Theodore Y. Ts&#x27;o
Date:Mon, 11 Sep 2000 13:08:59 + From: Pravir Chandra <[EMAIL PROTECTED]> I've been working to change the implementation of /dev/random over to the Yarrow-160a algorithm created by Bruce Schneier and John Kelsey. We've been working on parallel development for Linux and

Re: Availability of kdb

2000-09-12 Thread Theodore Y. Ts&#x27;o
On Mon, 11 Sep 2000, Jeff V. Merkey wrote: > > Thanks Ted. I know, but a kernel debugger is one of those nasty pieaces > of software that can quickly get out of sync if it's maintained > separately from the tree -- the speed at which changes occur in Linux > would render it a very difficult proj

Re: Availability of kdb

2000-09-12 Thread Theodore Y. Ts&#x27;o
Date: Mon, 11 Sep 2000 17:51:20 -0600 From: "Jeff V. Merkey" <[EMAIL PROTECTED]> I support source level in the kernel. Based on Andi Klein's review, I have grabbed ext2utils and am looking at a minimal int 0x13 interface to load files into memory. hardest problem here for Linux i

Re: [BUG] threaded processes get stuck in rt_sigsuspend/fillonedir/exit_notify

2000-09-12 Thread Theodore Y. Ts&#x27;o
Date:Mon, 11 Sep 2000 18:27:30 -0700 From: David Ford <[EMAIL PROTECTED]> > I've told Linus several times about this problems but he puts out one > test release after the other without this fixed. This is kinda important, I run DNS tools which are threaded amongst numer

Re: Using Yarrow in /dev/random

2000-09-12 Thread Theodore Y. Ts&#x27;o
Date: Tue, 12 Sep 2000 09:56:12 + From: Pravir Chandra <[EMAIL PROTECTED]> i agree that the yarrow generator does place some faith on the crypto cipher and the accumulator uses a hash, but current /dev/random places faith on a crc and urandom uses a hash. No, not true. The m

Re: Using Yarrow in /dev/random

2000-09-12 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 01:23:30 +0200 (CEST) From: Igmar Palsenberg <[EMAIL PROTECTED]> > No, not true. The mixing into the entropy pool uses a twisted LFSR, but > all outputs from the pool (to either /dev/random or /dev/urandom) > filters the output through SHA-1 as a whit

Re: Update Linux 2.4 Status/TODO list

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date: Tue, 12 Sep 2000 23:37:57 -0700 From: David Ford <[EMAIL PROTECTED]> > > 4. Boot Time Failures > > > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC > >Versa LX with PIIX tuning) > > If this is a rare version of the BX/LX that has a

Re: Update Linux 2.4 Status/TODO list

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 08:46:00 +0200 From: Harald Dunkel <[EMAIL PROTECTED]> How can I submit a bug report to be added to this list? I *try* to follow bug reports sent to Linux-kernel, but if you want to be sure, send it directly to me ([EMAIL PROTECTED]). (And now for the sta

Re: Update Linux 2.4 Status/TODO list

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date: Tue, 12 Sep 2000 23:55:55 -0700 From: David Ford <[EMAIL PROTECTED]> Please add 'APM resume returns the machine to the first tty, crashes X' This appeared w/ test8. If this is intended, I'd be very happy to know if so and I can write in to xfree86 about it. If not intend

Re: Update Linux 2.4 Status/TODO list

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date: Wed, 13 Sep 2000 10:03:39 +0200 From: Andries Brouwer <[EMAIL PROTECTED]> On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote: > 8. Fix Exists But Isnt Merged ... > 9. To Do > * Mount of new fs over existing mointpoint should return an error >

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 12:54:49 +0200 (CEST) From: Trond Myklebust <[EMAIL PROTECTED]> Don't forget that 2^20 > 10^6, hence if you really want units of microseconds, you actually only need to save 3 bytes worth of data per timestamp. For the purposes of NFS, however the

Re: Proposal: Linux Kernel Patch Management System

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 12:56:22 +0100 (BST) From: Alan Cox <[EMAIL PROTECTED]> > suggest a unique identifier for your patch? Humans are usually better > at picking sensible names than a machine, and in discussions, it is > better to refer to 'ide-foobar-fix3' than KP7562 ev

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date: Wed, 13 Sep 2000 22:35:10 +0200 (CEST) From: Trond Myklebust <[EMAIL PROTECTED]> You might be able to steal a couple of bytes and then rewrite ext2fs to mask those out from the 'i_generation' field, but it would mean that you could no longer boot your old 2.2.16 kernel withou

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

2000-09-14 Thread Theodore Y. Ts&#x27;o
From: "Albert D. Cahalan" <[EMAIL PROTECTED]> Date:Wed, 13 Sep 2000 19:20:42 -0400 (EDT) The ext2 inode has 6 obviously free bytes, 6 that are only used on filesystems marked as Hurd-type, and 8 that seem to be claimed by competing security and EA projects. So, being wastef

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Thu, 14 Sep 2000 15:09:35 +0200 (CEST) From: Trond Myklebust <[EMAIL PROTECTED]> Would it perhaps make sense to use one of these last 'free' fields as a pointer to an 'inode entension'? If you still want ext2fs to be able to accommodate new projects and ideas, then it seem

Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Thu, 14 Sep 2000 17:12:35 +0200 (MEST) From: [EMAIL PROTECTED] (Rogier Wolff) The "right" way to do this is to have a "this spot is in use, but you don't understand it" indication for an inode (*). The "expansion ptr" can then normally point to the directly following inode, b

Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Thu, 14 Sep 2000 17:03:11 +0200 (CEST) From: Trond Myklebust <[EMAIL PROTECTED]> For the timestamps, yes, but inode caching will take most of that hit. After all, the only time stat() reads from disk is when the inode has completely fallen out of the cache. For commonly used

Re: Quantum lct08 & Promise Ultra66

2000-09-14 Thread Theodore Y. Ts&#x27;o
From: "Mike" <[EMAIL PROTECTED]> Date:Thu, 14 Sep 2000 20:34:42 +0400 Just have compiled 2.4.0-test8 today... Nothing interesting Everything goes the same way as 2 test releases before... All my devices are detected right, but... :-( Kernel panic again at the file sys

Re: [PATCH] Re: [BUG] PCMCIA CardBus problems in 2.4.0-test8

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Wed, 13 Sep 2000 17:17:01 -0400 From: Jeff Garzik <[EMAIL PROTECTED]> I ran with the idea, and created the attached patch, against 2.4.0-test8. It converts serial.c to the new PCI API (quite compactly, I might add) It should be possible with this patch to now hotplug ser

Re: NFS locking bug -- limited mtime resolution means nfs_lock() doesnot provide coherency guarantee

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Fri, 15 Sep 2000 01:06:24 +0200 (MEST) From: [EMAIL PROTECTED] (Rogier Wolff) My suggestion is indeed effectivly (almost) doubling the inode size. However, it provides an upgrade path, where you can double-boot with a kernel that DOESN"T know about the inodes. The 2.2 kerne

Re: serial problems

2000-10-23 Thread Theodore Y. Ts&#x27;o
Date:Sat, 21 Oct 2000 23:45:58 +0200 From: octave klaba <[EMAIL PROTECTED]> I use the serial cart with 5.03 / 2.2.17 Serial driver version 5.03 (2000-08-11) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled 00:0d.0 Serial controller: Timedia Technology Co Ltd: Unknown device 716

Re: serial problems

2000-10-24 Thread Theodore Y. Ts&#x27;o
Date: Tue, 24 Oct 2000 11:14:13 +0200 From: octave klaba <[EMAIL PROTECTED]> > Can you actually give me some details of how your system "crashed"? It > certainly shouldn't have. Kermit will sometimes hang waiting for the > terminal to flush if it's enabled hardware flow control a

Re: 2.4.0-test10-pre6: Use of abs()

2000-11-01 Thread Theodore Y. Ts&#x27;o
Date: Wed, 1 Nov 2000 09:46:19 -0500 From: [EMAIL PROTECTED] On Mon, Oct 30, 2000 at 05:14:34PM +0100, Martin Dalecki wrote: > Of corse right! BTW. There are tons of places where log2 is calculated > explicitly in kernel which should be replaced with the corresponding > built

Re: non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?)

2000-11-02 Thread Theodore Y. Ts&#x27;o
Date:Thu, 02 Nov 2000 12:31:51 -0700 From: Tim Riker <[EMAIL PROTECTED]> Me or Alan? I did not mean this as a dig. I feel strongly that one should have the choice here. I do not choose to enforce my beliefs on anyone else. I am suggesting only that others should provide the

Re: non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?)

2000-11-02 Thread Theodore Y. Ts&#x27;o
Date: Thu, 02 Nov 2000 13:53:55 -0700 From: Tim Riker <[EMAIL PROTECTED]> As is being discussed here, C99 has some replacements to the gcc syntax the kernel uses. I believe the C99 syntax will win in the near future, and thus the gcc syntax will have to be removed at some point. In

Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land

2000-11-03 Thread Theodore Y. Ts&#x27;o
Date:Fri, 03 Nov 2000 14:44:17 -0500 From: [EMAIL PROTECTED] My problem is that pthread_create (glibc 2.1.3, kernel 2.2.17 i686) is failing because, deep inside glibc somewhere, nanosleep() is returning EINTR. Sounds like it might be a bug in pthread_create although th

Re: Can EINTR be handled the way BSD handles it? -- a plea from auser-land programmer...

2000-11-06 Thread Theodore Y. Ts&#x27;o
Date:Mon, 6 Nov 2000 09:13:25 -0500 (EST) From: George Talbot <[EMAIL PROTECTED]> I respectfully disagree that programs which don't surround some of the most common system calls with do { rv = __some_system_call__(...); } wh

Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer...

2000-11-07 Thread Theodore Y. Ts&#x27;o
From: Ulrich Drepper <[EMAIL PROTECTED]> Date: 06 Nov 2000 10:50:37 -0800 > Arguably though the bug is in glibc, in that if it's using signals > behinds the scenes, it should have passed SA_RESTART to sigaction. Why are you talking such a nonsense? The claim was made that pthrea

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-09 Thread Theodore Y. Ts&#x27;o
Date:Thu, 9 Nov 2000 13:39:04 + (GMT) From: Paul Jakma <[EMAIL PROTECTED]> I actually think Linus has been too loose/vague on modules. The official COPYING txt file in the tree contains an exception on linking to the kernel using syscalls from linus and the GPL. nothing

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-09 Thread Theodore Y. Ts&#x27;o
Date:Thu, 09 Nov 2000 08:43:14 -0500 From: Michael Rothwell <[EMAIL PROTECTED]> And how would a hypothetical Advanced Linux Kernel Project be different? Set aside the GKHI and the issue of binary-only hook modules; how would an "enterprise" fork be any different than RT or

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-09 Thread Theodore Y. Ts&#x27;o
Date:Wed, 08 Nov 2000 16:35:33 -0500 From: Michael Rothwell <[EMAIL PROTECTED]> Sounds great; unfortunately, the core group has spoken out against a modular kernel. This is true; that's because a modular kernel means that interfaces have to be frozen in time, usually forever.

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-09 Thread Theodore Y. Ts&#x27;o
Date: Thu, 9 Nov 2000 14:26:33 + (GMT) From: Alan Cox <[EMAIL PROTECTED]> > Actually, he's been quite specific. It's ok to have binary modules as > long as they conform to the interface defined in /proc/ksyms. What is completely unclear is if he has the authority to say tha

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-10 Thread Theodore Y. Ts&#x27;o
From: [EMAIL PROTECTED] Date:Fri, 10 Nov 2000 11:41:09 + It has the potential to to make patches easier to re-work for different kernel versions, and to enable development maintence and fixing of the patch to be done independently of a kernel build. And it also has the

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

2000-11-10 Thread Theodore Y. Ts&#x27;o
Date: Fri, 10 Nov 2000 10:36:31 -0800 From: "Matt D. Robinson" <[EMAIL PROTECTED]> As soon as I finish writing raw write disk routines (not using kiobufs), we can _maybe_ get LKCD accepted one of these days, especially now that we don't have to build 'lcrash' against a kernel revis

Re: Serial cardbus code.... for testing, please.....

2000-12-08 Thread Theodore Y. Ts&#x27;o
Date: Fri, 8 Dec 2000 13:27:51 -0800 (PST) From: Linus Torvalds <[EMAIL PROTECTED]> I didn't have time to do more than just quickly apply the patch and leave in a hurry, but my Vaio certainly recognized the serial port on the combo cardbus card I have with this patch. Everything lo

Re: Serial cardbus code.... for testing, please.....

2000-12-09 Thread Theodore Y. Ts&#x27;o
Date: Fri, 8 Dec 2000 23:41:54 -0800 (PST) From: Linus Torvalds <[EMAIL PROTECTED]> This is a problem that many drivers have: when the card is removed, the driver sees an interrupt (which happens to be the CardBus card removal interrupt, but the serial driver doesn't know that, and

Re: Serial cardbus code.... for testing, please.....

2000-12-09 Thread Theodore Y. Ts&#x27;o
Date: Sat, 9 Dec 2000 10:13:50 -0800 (PST) From: Linus Torvalds <[EMAIL PROTECTED]> I checked my VAIO's, and they all have a Ricoh cardbus bridge. Ted claimed he had a TI1311 or something, I think. So his VAIO is definitely different from the ones I have. That may be enough of a

Re: Serial cardbus code.... for testing, please.....

2000-12-10 Thread Theodore Y. Ts&#x27;o
Date: Sat, 09 Dec 2000 11:13:59 -0500 From: Jeff Garzik <[EMAIL PROTECTED]> > Note how the "rs_interrupt()" routine _tries_ to avoid this by having a > pass counter value, but that logic never triggers because we will loop > forever in receive_chars(), so the rs_interrupt() counter

Re: Signal 11

2000-12-15 Thread Theodore Y. Ts&#x27;o
Date:Fri, 15 Dec 2000 01:09:29 + (GMT) From: Alan Cox <[EMAIL PROTECTED]> > > oWe tell vendors to build RPMv3 , glibc 2.1.x > Curious HOW do you tell vendors?? When they ask. More usefully Dan Quinlann and most vendors put together a recommended set of thing

Re: /dev/random: really secure?

2000-12-18 Thread Theodore Y. Ts&#x27;o
Date:Mon, 18 Dec 2000 21:38:01 +0100 From: Jamie Lokier <[EMAIL PROTECTED]> David Schwartz wrote: > The code does its best to estimate how much actual entropy it is gathering. A potential weakness. The entropy estimator can be manipulated by feeding data which looks ra

Re: /dev/random: really secure?

2000-12-19 Thread Theodore Y. Ts&#x27;o
Date: Tue, 19 Dec 2000 12:49:48 +0100 From: Kurt Garloff <[EMAIL PROTECTED]> On Mon, Dec 18, 2000 at 04:33:13PM -0500, Theodore Y. Ts'o wrote: > Note that writing to /dev/random does *not* update the entropy estimate, > for this very reason. The assumption is t

Re: ext2 caches

2000-09-29 Thread Theodore Y. Ts&#x27;o
Date:Fri, 29 Sep 2000 19:24:01 +0200 From: Frederic Magniette <[EMAIL PROTECTED]> We would like to do some operations on a ext2 disk while it is mounted read-only. The problem is that our operations have no effects because everithing is cached. Is it possible to shrink al

Re: reading 1 hardsector size, not one block size

2000-09-29 Thread Theodore Y. Ts&#x27;o
Date:Fri, 29 Sep 2000 17:49:04 -0600 From: "Jeff V. Merkey" <[EMAIL PROTECTED]> This is going to be a continuing problem for non-Unix file systems like NTFS and NWFS that rely on the ability to read and write variable length sector runs. It's not just non-Unix file syste

Re: What is up with Redhat 7.0?

2000-09-29 Thread Theodore Y. Ts&#x27;o
Date:Sat, 30 Sep 2000 04:10:59 +0200 From: Marc Lehmann <[EMAIL PROTECTED]> Do you really think that explicitly supporting broken distributions (redhat 7.0 comes with a experimental snapshot of gcc which is neither binary compatible to 2.95 nor to 3.0, cutting binary compat

Re: reading 1 hardsector size, not one block size

2000-09-29 Thread Theodore Y. Ts&#x27;o
Date: Fri, 29 Sep 2000 22:16:53 -0700 (PDT) From: Andre Hedrick <[EMAIL PROTECTED]> Basically you can de-stroke a drive with what you let the OS/FS report. Once this is done there is no way any FS can get to the stuff beyond what it knows about. I'm not sure what you mean by "de-s

Re: Proposal: Linux Kernel Patch Management System

2000-09-14 Thread Theodore Y. Ts&#x27;o
Date: Thu, 14 Sep 2000 15:45:24 -0700 From: Larry McVoy <[EMAIL PROTECTED]> I'm going to have to respectfully disagree. First of all, having a flag day where everyone switches to BK just isn't a realistic expectation, even if the license wasn't an issue. Things just don't work

Re: Proposal: Linux Kernel Patch Management System

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 03:30:39 -0700 From: "David S. Miller" <[EMAIL PROTECTED]> From: Daniel Quinlan <[EMAIL PROTECTED]> Date: Wed, 13 Sep 2000 03:18:14 -0700 (PDT) How exactly does a system to tracking patches and bugs/fixes (not to mention helping Lin

Re: Proposal: Linux Kernel Patch Management System

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date:Wed, 13 Sep 2000 02:27:07 -0700 From: "David S. Miller" <[EMAIL PROTECTED]> rsync [EMAIL PROTECTED]:/home/torvalds/src/linux \ ftp.kernel.org:/pub/linux/kernel/LIVE/linux would be the real helper for people like me whose only real issue now is bothering Lin

Re: Proposal: Linux Kernel Patch Management System

2000-09-13 Thread Theodore Y. Ts&#x27;o
From: "Dunlap, Randy" <[EMAIL PROTECTED]> Date: Wed, 13 Sep 2000 09:17:55 -0700 I appreciate Alan and you doing the kernel Status/TODO lists, but I think that you ought to simplify it for yourself at least (not that this would help Linus) by having maintainers do it instead of y

Re: Proposal: Linux Kernel Patch Management System

2000-09-13 Thread Theodore Y. Ts&#x27;o
Date: Wed, 13 Sep 2000 17:14:57 +0200 (MEST) From: [EMAIL PROTECTED] (Rogier Wolff) Today we fixed a problem in a driver we maintain here. We should've gone ahead and generate the patch and queued it for Linus. However, in reality we'd like the complaining customer to test the pat

Re: tty_[un]register_devfs putting 3K structures on the stack

2000-10-06 Thread Theodore Y. Ts&#x27;o
Date:Fri, 06 Oct 2000 12:01:34 -0500 From: Jeff Dike <[EMAIL PROTECTED]> tty_register_devfs and tty_unregister_devfs both declare "struct tty_struct" locals. According to gdb: (gdb) p sizeof(struct tty_struct) $20 = 3084 This eats up most of a 4K page, and on UML t

Re: [PATCH] ext4/mballoc: Remove unneeded variable "err"

2018-08-04 Thread Theodore Y. Ts&#x27;o
On Sat, Aug 04, 2018 at 07:04:56PM +0800, zhong jiang wrote: > The err is not used after initalization. So just remove the variable. > > Signed-off-by: zhong jiang I'll apply this patch, but how did you generate the diff? The function name here is all wrong: > diff --git a/fs/ext4/mballoc.c b/

Re: [PATCH] ext4/mballoc: Remove unneeded variable "err"

2018-08-05 Thread Theodore Y. Ts&#x27;o
On Sun, Aug 05, 2018 at 08:59:33PM +0800, zhong jiang wrote: > I create the diff in this patch again ,but get the same result . > the git version is git version 1.7.12.4 but I create the diff in > git version 1.8.3.1. It shows the correct function name. Ah, OK, so it was a git bug. Whew! Glad

Re: [PATCH 4.14 222/246] ext4: fix check to prevent initializing reserved inodes

2018-08-08 Thread Theodore Y. Ts&#x27;o
On Wed, Aug 08, 2018 at 07:28:45AM +0200, Greg Kroah-Hartman wrote: > On Wed, Aug 08, 2018 at 12:17:30AM +0200, Matthias Schiffer wrote: > > On 08/01/2018 06:52 PM, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > > > know. > > > > It seems

[GIT PULL] ext4 updates for 4.19

2018-08-13 Thread Theodore Y. Ts&#x27;o
The following changes since commit 5012284700775a4e6e3fbe7eac4c543c4874b559: ext4: fix check to prevent initializing reserved inodes (2018-07-29 15:34:00 -0400) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus for you

Re: Remounting filesystem read-only

2018-07-27 Thread Theodore Y. Ts&#x27;o
On Fri, Jul 27, 2018 at 12:26:25PM -0700, Sodagudi Prasad wrote: > On 2018-07-26 18:04, Sodagudi Prasad wrote: > > Hi All, > > > > +linux-kernel@vger.kernel.org list. > > Hi All, > > Observing the following issue with one of the partition on android device > with 4.14.56 kernel. When I try to

Re: [PATCH] tracing: do not leak kernel addresses

2018-07-27 Thread Theodore Y. Ts&#x27;o
More generally, stupid question, but does Android *really* need to have debugfs mounted? And if so, can we figure out what facilities that are needed and can we find some other way of meeting those requirements? - Ted

Re: [PATCH] tracing: do not leak kernel addresses

2018-07-27 Thread Theodore Y. Ts&#x27;o
On Fri, Jul 27, 2018 at 04:11:03PM -0400, Steven Rostedt wrote: > That said, I would assume that > other Android utilities are using other debugfs files for system > status and such. Yeah, I know we probably have lost the "debugfs is only for debugging and has no place in a production system" batt

Re: [PATCH] tracing: do not leak kernel addresses

2018-07-27 Thread Theodore Y. Ts&#x27;o
On Fri, Jul 27, 2018 at 03:05:43PM -0700, Sandeep Patil wrote: > On Fri, Jul 27, 2018 at 04:21:14PM -0400, Theodore Y. Ts'o wrote: > > On Fri, Jul 27, 2018 at 04:11:03PM -0400, Steven Rostedt wrote: > > > That said, I would assume that > > > other Android utiliti

Re: Remounting filesystem read-only

2018-07-27 Thread Theodore Y. Ts&#x27;o
On Fri, Jul 27, 2018 at 01:34:31PM -0700, Sodagudi Prasad wrote: > > The error should be pretty clear: "Inode table for bg 0 marked as > > needing zeroing". That should never happen. > > Can you provide any debug patch to detect when this corruption is happening? > Source of this corruption and h

[GIT PULL] random fixes for 4.18-rc7

2018-07-28 Thread Theodore Y. Ts&#x27;o
The following changes since commit 1e4b044d22517cae7047c99038abb23243ca: Linux 4.18-rc4 (2018-07-08 16:34:02 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus_stable for you to fetch changes up to 81e69df

Re: [PATCH v2] ext4: use swap macro in mext_page_double_lock

2018-07-29 Thread Theodore Y. Ts&#x27;o
On Thu, Jul 26, 2018 at 12:43:23PM -0500, Gustavo A. R. Silva wrote: > Make use of the swap macro and remove unnecessary variable *tmp*. > This makes the code easier to read and maintain. > > This code was detected with the help of Coccinelle. > > Signed-off-by: Gustavo A. R. Silva Thanks, appl

Re: [PATCH v2] ext4: mballoc: Fix spectre gadget in ext4_mb_regular_allocator

2018-07-30 Thread Theodore Y. Ts&#x27;o
Hey Jeremy, I think you are also going to be changing the 1/3 patch from the original patch series that this was part of. That's correct, right? It would be easier for me if you could simply make all of the revisions you plan to make for the patch series, and then upload a full v2 of the entire

Re: [PATCH v2] ext4: mballoc: Fix spectre gadget in ext4_mb_regular_allocator

2018-07-30 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 30, 2018 at 02:46:59PM -0400, Jeremy Cline wrote: > I dropped patch 1/3 and 2/3 from the original series because they can > both be covered by some sanitation in fs/quota/quota.c, so the this is > only patch from the v1 series that should be applied. > > Sorry for not being more clear!

Re: [PATCH] random: Remove preempt disabled region

2018-07-22 Thread Theodore Y. Ts&#x27;o
On Wed, Jul 11, 2018 at 04:37:21PM +0200, Sebastian Andrzej Siewior wrote: > From: Ingo Molnar > > No need to keep preemption disabled across the whole function. > > mix_pool_bytes() uses a spin_lock() to protect the pool and there are > other places like write_pool() whhich invoke mix_pool_byte

Re: [PATCH] ext4: remove abnormal set for I_DATA_SEM subclass

2018-07-22 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 09, 2018 at 04:58:28PM +0900, Junil Lee wrote: > The -EBUSY return value of dquot_enable() function means that just > want to update flags. If some users make a duplicate request to update > flags, lockdep could catch the false positive casued by needing to > allocate a quota block from

Re: [PATCH] fs: ext4: use new return type vm_fault_t

2018-07-22 Thread Theodore Y. Ts&#x27;o
On Sat, Jul 07, 2018 at 04:00:30PM +0530, Souptick Joarder wrote: > Use new return type vm_fault_t for fault handler > ext4_filemap_fault. > > Signed-off-by: Souptick Joarder Thanks, applied. - Ted

Re: [PATCH] ext4: use swap macro in mext_page_double_lock

2018-07-22 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 09, 2018 at 08:16:00AM -0500, Gustavo A. R. Silva wrote: > Make use of the swap macro and remove unnecessary variable *tmp*. > This makes the code easier to read and maintain. Also, reduces the > stack usage. > > This code was detected with the help of Coccinelle. > > Signed-off-by: G

Re: [PATCH] ext4: fix warning message to output correct type.

2018-07-22 Thread Theodore Y. Ts&#x27;o
On Fri, Jul 13, 2018 at 06:15:47PM +0900, Junichi Uekawa wrote: > Output the warning message before we clobber type and be -1 all the time. > The error message would now be > > [1.519791] EXT4-fs warning (device vdb): ext4_enable_quotas:5402: > Failed to enable quota tracking (type=0, err=-3).

Re: [PATCH 36/38] vfs: Add a sample program for the new mount API [ver #10]

2018-07-30 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 30, 2018 at 12:49:38PM -0700, Matthew Wilcox wrote: > > That said, people have wanted these kinds of extended error > > descriptors forever, and the reason we haven't added them is that it > > generally is more pain than it is necessarily worth. I'm not actually > > at all convinced tha

Re: [PATCH 36/38] vfs: Add a sample program for the new mount API [ver #10]

2018-07-30 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 30, 2018 at 04:58:49PM -0700, Matthew Wilcox wrote: > > Way to poison the well by calling it VMS-style error reporting! As I > understand it though, VMS reported errors in English with an error code > that could be looked up in The Wall of documentation. I'd see David's > proposal as

Re: [PATCH] ext4: Convert int to vm_fault_t type

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Sat, Jul 28, 2018 at 02:20:00PM +0530, Souptick Joarder wrote: > Use new return type vm_fault_t for ext4_page_mkwrite > handler and block_page_mkwrite_return. > > Signed-off-by: Souptick Joarder FYI, this patch was very sloppy, and didn't do the right thing. That's because of how you messed

Re: [PATCH] ext4: Convert int to vm_fault_t type

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Wed, Aug 01, 2018 at 06:56:39PM +0530, Souptick Joarder wrote: > As caller of block_page_mkwrite() are - > fs/ext4/inode.c > fs/nilfs2/file.c > > I will merge both changes in a single patch and send it. Note that it's *important* for ext4 that we know what kind of error was returned by the hel

Re: [PATCH] ext4: Convert int to vm_fault_t type

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Wed, Aug 01, 2018 at 10:38:30AM -0400, Theodore Y. Ts'o wrote: > I'm going to drop the whole ext4 changes for vm_fault_t for this > cycle, and I'll let you try to fix it up properly for the next cycle. Here's the fixed up commit that I'm going to drop since y

Re: [PATCH] ext4: Convert int to vm_fault_t type

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Wed, Aug 01, 2018 at 09:13:19AM -0700, Matthew Wilcox wrote: > On Wed, Aug 01, 2018 at 12:06:18PM -0400, Theodore Y. Ts'o wrote: > > On Wed, Aug 01, 2018 at 10:38:30AM -0400, Theodore Y. Ts'o wrote: > > > I'm going to drop the whole ext4 changes for vm_fault_t f

Re: [PATCH 1/5] vfs: syscall: Add fsinfo() to query filesystem information

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Wed, Aug 01, 2018 at 05:14:01PM +0100, David Howells wrote: > > Some attributes (such as the servers backing a network filesystem) can have > multiple values. These can be enumerated by setting params->Nth and > params->Mth to 0, 1, ... until ENODATA is returned. How does the caller know whet

Re: [PATCH v2] ext4: mballoc: Fix spectre gadget in ext4_mb_regular_allocator

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 30, 2018 at 06:07:47PM +, Jeremy Cline wrote: > 'ac->ac_g_ex.fe_len' is a user-controlled value which is used in the > derivation of 'ac->ac_2order'. 'ac->ac_2order', in turn, is used to > index arrays which makes it a potential spectre gadget. Fix this by > sanitizing the value ass

Re: [PATCH] Improve code readability

2018-08-01 Thread Theodore Y. Ts&#x27;o
On Tue, Jul 31, 2018 at 02:15:15PM +0800, Liu Song wrote: > Merge the duplicated complex conditions to improve code readability. > > Signed-off-by: Liu Song > Reviewed-by: Jiang Biao Thanks, applied. - Ted

Re: [PATCH] ext4: remove abnormal set for I_DATA_SEM subclass

2018-07-23 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 23, 2018 at 10:48:37AM +0900, 이준일/연구원/MC연구소 BSP실 BSP6팀(junil0814@lge.com) wrote: > Then, I have a question. > quotactl() doesn't have case only to set limits flag, the routine to set > the DQUOT_LIMITS_ENABLED flag is under dquot_enable() function. > According to this logic, if use

Re: Does /dev/urandom now block until initialised ?

2018-07-23 Thread Theodore Y. Ts&#x27;o
On Mon, Jul 23, 2018 at 12:11:12PM -0400, Jeffrey Walton wrote: > > I believe Stephan Mueller wrote up the weakness a couple of years ago. > He's the one who explained the interactions to me. Mueller was even > cited at https://github.com/systemd/systemd/issues/4167. Stephan had a lot of complain

Re: no public email address excluding Gmail

2018-07-25 Thread Theodore Y. Ts&#x27;o
On Wed, Jul 25, 2018 at 03:25:07PM +0800, 张宁 wrote: > Hi, everyone > > I notice each developer in this email list has a company email address > or Gmail, or maybe selfhosted email. > > last night I have tried my outlook.com, yahoo.com, QQ.com email, all > of them are rejected by mechine. There a

Re: [PATCH 24/32] vfs: syscall: Add fsopen() to prepare for superblock creation [ver #9]

2018-07-12 Thread Theodore Y. Ts&#x27;o
On Thu, Jul 12, 2018 at 10:26:37PM +0100, David Howells wrote: > The problem is that there's more than one actual "open" involved. > > fd = fsopen("ext4");<--- #1 > whatever_interface(fd, "s /dev/sda1"); > whatever_interface(fd, "o journal_path=/dev/sd

Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap

2018-07-12 Thread Theodore Y. Ts&#x27;o
> > Review console log and on each run I have filesystem rebuild. The problem > is that mke2fs I am using is 1.44.3-rc2. I am now reseting the environment > and re-test. > Could it be that you saw the error in ext4_validate_block_bitmap()? The patch which I sent Dann only fixed the problem for in

  1   2   3   4   5   6   >