On Tue, Jun 19, 2007 at 08:51:25PM +0200, Karel Zak wrote:
> > > I don't think that mtab is a good place for this shared subtree
> > > stuff. The mtab needs to die.
> >
> > Perhaps. Perhaps not.
> >
> > On the one hand I think there is a place for arbitrary user-space info
> > about mounted fil
On Tue, Jun 19, 2007 at 04:15:28PM +0200, Karel Zak wrote:
> We use GIT for development, the utils/util-linux-ng is for releases.
Aha - and there have not been any releases yet.
> > Anyway, Dirk Gerrits, Ren?? Gabri??l and Peter Kooijmans sent me
I meant Dirk Gerrits, Ren?? Gabri??ls and Peter
On Sat, Jun 02, 2007 at 08:55:13PM +0200, Jonathan Schleifer wrote:
> This patch adds a new kernel parameter (ignore_partitions=device) to
> the kernel. It is useful when using a fake RAID with dmraid so that
> Linux won't complain about attemps to access the drive beyond its
> boundaries when ude
On Fri, May 04, 2007 at 11:18:37PM +0400, Sergei Shtylyov wrote:
> HPT36x chip don't seem to have the channel enable bits,
> so prevent the IDE core from checking them...
>
> Signed-off-by: Sergei Shtylyov <[EMAIL PROTECTED]>
Earlier this evening I reported that HPT366 was broken in 2.6.21.
I con
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
> I'm having problems with a font I just created. It's a rather big one,
> intended for a framebuffer console in UTF-8 mode. The strace program
> reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
> In reading the kernel
On Sat, Apr 07, 2007 at 01:27:09PM -0400, John Anthony Kazos Jr. wrote:
> From: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
>
> improves help text for MSDOS_PARTITION in fs/partitions/Kconfig.
> @@ -108,7 +112,11 @@ config MSDOS_PARTITION
> bool "PC BIOS (MSDOS partition tables) support" if
On Sat, Jan 20, 2007 at 09:08:47AM +0100, Michał Kudła wrote:
> Hello,
> after
> ...
> hdb: max request size: 512KiB
> hdb: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63,
>
> Should be everywere KiB, MiB, GiB, ... according to IEC 60027-2
You are mistaken. The MB here are ac
>> You were right, even after making the changes, it seems to be
>> telling lies:
>>
>> # mount
>> /dev/hda2 on / type ext2 (rw,usrquota)
Roughly speaking:
/etc/mtab shows you what you said to mount.
/proc/mounts shows what the current kernel state is.
These may differ greatly.
For all filesys
On Fri, Jan 12, 2007 at 06:18:00PM -0500, Kris Karas wrote:
> Hello Andries,
>
> I noticed you're listed as the maintainer for the disk
> geometry/partitioning logic in the 2.6 kernel, so I'm sending this to
> you, as I think this bug is most likely in that part of the code, ...
>
> I've been bug
On Mon, Jan 08, 2007 at 04:06:53PM -0800, Andrew Morton wrote:
> Daniel, it'd be good if you could review and test these changes please.
>
> Also, a signed-off-by from yourself and from Andries, please...
Signed-off-by: Andries Brouwer <[EMAIL PROTECTED]>
Andries
-
To u
On Fri, Apr 01, 2005 at 07:18:52PM +0200, Uwe Zybell wrote:
> There is a line in fs/partitions/msdos.c that lets extended partitions
> be max 1k (..."==1 ? 1 : 2"...). The comment explains it to protect
> sysadmins from themselves. But now I have found a legitimate use
> for extended partitions
On Mon, Mar 28, 2005 at 12:02:52PM -0800, Chris Wright wrote:
> * Pekka Enberg ([EMAIL PROTECTED]) wrote:
> > This patch removes macro obfuscation from fs/isofs/rock.c and cleans it up
> > a bit to make it more readable and maintainable. There are no functional
> > changes, only cleanups. I have on
On Wed, Mar 23, 2005 at 03:20:55PM -0800, Andrew Morton wrote:
> Nothing beats poking around in a dead machine's guts with kgdb though.
Everyone his taste.
But I was surprised by
> SwapTotal: 1052216 kB
> SwapFree: 1045984 kB
Strange that processes are killed while lots of swap is ava
> "Alan Curry" <[EMAIL PROTECTED]> wrote:
>>
>> With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously,
>> a block cursor could be selected by
>> echo Cursor 0-31 >> /etc/TextConfig ; SVGATextMode
>> and the cursor would be a block. On all consoles. Forever.
>>
>> To accomp
On Mon, Mar 14, 2005 at 10:44:31AM -0600, Berkley Shands wrote:
> With a Broadcom BC4852 and suitable Sata drives, it is easy to create
> functional devices with well in excess of 2TB raw space. This presents a
> severe
> problem to partitioning tools, such as fdisk/cfdisk and the like as t
On Wed, Mar 09, 2005 at 03:14:36PM -0800, Nick Stoughton wrote:
> On Linux, the link() system call does not dereference symbolic links
>
> This behavior does not conform to POSIX
>
> Most Unix implementations behave in the manner specified by POSIX. One
> notable exception is Solaris 8 (I don't
On Wed, Mar 09, 2005 at 04:55:27PM +, Alan Cox wrote:
> > [PATCH] remove dead cyrix/centaur mtrr init code
>
> This patch was discussed previously and declared incorrect. The ->init
> method call is missing in the base mtrr code.
>
> Should be reverted and/or fixed properly.
Hi Alan - a
On Sat, Mar 05, 2005 at 10:35:24PM +0100, Alexander Nyberg wrote:
> 2.6.3-mm1 'dm-crypt vs. cryptoloop' discussion was some time ago, it is
> time to bring this up again:
> http://kerneltrap.org/node/2433
Are you a troll?
This is not something to be quoted by anybody serious.
Andrew referred to
On Fri, Mar 04, 2005 at 02:21:46PM -0800, Greg KH wrote:
> Anything else anyone can think of? Any objections to any of these?
> I based them off of Linus's original list.
>
> thanks,
>
> greg k-h
>
> --
>
> Rules on what kind of patches are accepted, and what ones are not, into
> the "lin
On Fri, Mar 04, 2005 at 12:44:31PM -0800, Andrew Morton wrote:
> Here's the list of things which we might choose to put into 2.6.11.2.
...
> nfsd--exportfs-reduce-stack-usage.patch
...
Different people want different things with our 2.6.x.y.
I would hope that criteria include (i) patch is obvious
Ha - a nice big thread. Issues include trivial fixes, testing,
and API stability.
-
About trivial fixes:
davem: the day Linus releases we always get a pile of "missing MODULE_EXPORT()"
type bug reports that are one liner fixes.
davej: So what was broken with the 2.6.8.1 type of release
On Wed, Mar 02, 2005 at 01:45:43PM +, Alan Cox wrote:
> On Mer, 2005-03-02 at 08:02, Dave Jones wrote:
> > If there are any of them still being used out there, I'd be even
> > more surprised if they're running 2.6. Then again, there are
> > probably loonies out there running it on 386/486's. 8
On Tue, Mar 01, 2005 at 11:52:44PM +, Alan Cox wrote:
> On Llu, 2005-02-28 at 19:20, Andries Brouwer wrote:
> > One such case is the mtrr code, where struct mtrr_ops has an
> > init field pointing at __init functions. Unless I overlook
> > something, this case may be easy
On Mon, Feb 28, 2005 at 08:35:29PM +0100, Adrian Bunk wrote:
> Hi Andries,
>
> your patch has many overlappings with a patch of mine aleady in -mm
> (both none of the two patches is a subset of the other one).
>
> Nowadays, working against -mm often avoids duplicate work.
>
> cu
> Adrian
As fa
There are several cases where __init function pointers are
stored in a general purpose struct. For example, a SCSI
template may contain a __init detect function.
Have not yet thought of an elegant way to avoid this.
One such case is the mtrr code, where struct mtrr_ops has an
init field pointing a
On Mon, Feb 28, 2005 at 01:55:28PM +0100, [EMAIL PROTECTED] wrote:
> Avoid changing the state of the console two times in some cases.
A bad change for several reasons.
(i) more object code is generated
(ii) the code is slower
(iii) you change something
Straight line code is cheap, jumps are exp
The file include/sound/yss225.h is unused.
It is more or less identical to sound/oss/yss225.h,
used by sound/oss/wavfront.c.
# rm include/sound/yss225.h
Andries
(Maybe this file is a remains from an attempt to consolidate
sound/oss/yss225.c and sound/isa/wavefront/wavefront_fx.c -
it is true t
On Sun, Feb 27, 2005 at 03:04:31AM +0100, Matthias Kunze wrote:
+config DEFAULT_CONSOLE_LOGLEVEL
You do not want to add yet another config option.
Config options are used to select or deselect major subsystems,
or support for specific hardware.
Not to tweak variables.
Adding more config variable
On Sun, Feb 27, 2005 at 01:47:43AM +0100, Uwe Bonnes wrote:
> on a Suse 9.2 System with Suse Hotplug, the phantom partition was somehow
> recognized as Reiserfs, and then the Hotplug mechanism trying to mount the
> bogus partition as a Reiser Filesystem ended in an Oops...
Always report the oops
On Sat, Feb 26, 2005 at 03:46:03PM -0800, Linus Torvalds wrote:
> We should probably do the same for the
> extended partition case, just to be consistent.
True.
diff -uprN -X /linux/dontdiff a/fs/partitions/msdos.c b/fs/partitions/msdos.c
--- a/fs/partitions/msdos.c 2004-12-29 03:39:55.
On Sat, Feb 26, 2005 at 03:12:28PM -0800, Linus Torvalds wrote:
> > The default fdisk will assign type 83 to a newly created partition.
>
> Ok. Is that a "it has done so for the last 5 years" thing?
The last twelve years.
> > (About type 0: DOS has used type 0 as definition of unused. It is no
On Sat, Feb 26, 2005 at 02:28:45PM -0800, Linus Torvalds wrote:
> Would it not make more sense to just sanity-check the size itself, and
> throw it out if the partition size (plus start) is bigger than the disk
> size?
I don't mind.
> There might well be people use use partition type 0, just bec
A well-known kernel bug is that it guesses at the partition type
and the partitions on any disk it encounters. This is bad because
needless I/O is done, slowing down the boot, sometimes quite a lot,
especially when I/O errors occur. And it is bad because sometimes
we guess wrong.
In other words, w
setup_APIC_timer is only called in __init context and uses __initdata
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++ b/arch/i386/kernel/apic.c 2005-02-26 16:13:21.0 +0100
wait_timer_tick refers to the __init functions wait_8254_wraparound
or wait_hpet_tick, hence must be __initdata.
Andries
diff -uprN -X /linux/dontdiff a/arch/i386/kernel/apic.c
b/arch/i386/kernel/apic.c
--- a/arch/i386/kernel/apic.c 2005-02-26 12:13:28.0 +0100
+++ b/arch/i386/kernel/ap
scsi_dev_flags is referred to in
module_param_string(dev_flags, scsi_dev_flags, sizeof(scsi_dev_flags), 0);
Andries
diff -uprN -X /linux/dontdiff a/drivers/scsi/scsi_devinfo.c
b/drivers/scsi/scsi_devinfo.c
--- a/drivers/scsi/scsi_devinfo.c 2004-12-29 03:39:47.0 +0100
+++ b/drivers/
cfq_init() calls __init cfq_slab_setup and hence must be __init itself
also made it static
Andries
diff -uprN -X /linux/dontdiff a/drivers/block/cfq-iosched.c
b/drivers/block/cfq-iosched.c
--- a/drivers/block/cfq-iosched.c 2005-02-26 12:13:29.0 +0100
+++ b/drivers/block/cfq-iosche
parport_init_mode is referred to in int __devinit sio_via_probe().
Andries
diff -uprN -X /linux/dontdiff a/drivers/parport/parport_pc.c
b/drivers/parport/parport_pc.c
--- a/drivers/parport/parport_pc.c 2005-02-26 12:13:30.0 +0100
+++ b/drivers/parport/parport_pc.c 2005-02-26 14
On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote:
> > SuSE 9.1
> > Vendor: easyRAID Model: X16 Rev: 0001
> > Type: Direct-Access ANSI SCSI revision: 03
> > scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than
> > currently supported.
>
> Looks like random garbage.
On Wed, Feb 16, 2005 at 07:20:35PM +0100, Jirka Bohac wrote:
> Now ... are there any more suggestions for any of the patches?
For the time being I look only at the diacr for unicode part.
The fragment below looks like a strange kludge.
> - if (diacr)
> - value = handle_diacr(vc,
On Wed, Feb 09, 2005 at 06:19:21PM +0100, Jirka Bohac wrote:
> There are presently two ways around this, neither of them good enough
> 1) assigning one of the other modifier keysyms to the CapsLock key
>-- the LED will not work
True.
> But by adding two modifiers to almost every keyboard ma
On Wed, Feb 09, 2005 at 05:55:00PM +0100, Vojtech Pavlik wrote:
> On Wed, Feb 09, 2005 at 05:38:56PM +0100, Andries Brouwer wrote:
>> On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
>>
>>>> It seems very unlikely that you cannot handle Czech with all
On Wed, Feb 09, 2005 at 05:03:45PM +0100, Vojtech Pavlik wrote:
> > It seems very unlikely that you cannot handle Czech with all
> > combinations of 8 keys pressed, and need 9.
>
> A czech keyboard has the letters 'escrzyaie' with accents on the number
> row of keys. With a Shift, they are suppos
On Wed, Feb 09, 2005 at 02:26:54PM +0100, Jirka Bohac wrote:
> Hi folks,
>
> find attached a patch that improves the keycode to keysym mapping in the
> kernel. The current system has its limits, not allowing to implement keyboard
> maps that people in different countries are used to. This patch tr
On Tue, Feb 08, 2005 at 02:57:07PM -0800, cliff white wrote:
> Running 2.6.10-ac10 on the STP 1-CPU machines, we don't seem to be able to
> complete
> a kernbench run without hitting the OOM-killer. ( kernbench is multiple
> kernel compiles,
> of course ) Machine is 800 mhz PIII with 1GB memory.
On Mon, Feb 07, 2005 at 03:53:00PM +0900, Clemens Schwaighofer wrote:
> >>Yeah, but the link order could be changed... Patch inlined.
> >
> > And just what does the link order (or changes thereof) have to do with that?
>
> because some distributions (eg gentoo) make a symlink to /proc/filesystem
On Mon, Feb 07, 2005 at 09:10:38AM -0500, Pavel Fedin wrote:
> Nobody answered so i repeat the question.
> I think i found a way to make use of NLS table for HFS filesystem and
> i'm going to try to implement it. But first i need to create NLS module
> for codepage 10007 (Mac cyrillic). In the b
On Thu, Feb 03, 2005 at 03:18:20PM +0100, Fruhwirth Clemens wrote:
> (Actually it's a Multi Time Pad.)
And you call this "crypto"?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.or
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
> I ran badblocks (all night). There were none. It's a SCSI disk
> and it requires chunks of DMA RAM for each write. The machine
> just croaks when it gets low on RAM and tries to write to
> SCSI swap which requires RAM.
In some other post
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
>
> When I compile and run the following program:
>
> #include
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
>
> ... the following occurs after about 30 seconds (your mileage
> may vary):
>
> Additional s
On Tue, Feb 01, 2005 at 01:14:39AM +0900, OGAWA Hirofumi wrote:
> Andries Brouwer <[EMAIL PROTECTED]> writes:
> > On Sun, Jan 30, 2005 at 09:25:33PM -0800, Andrew Morton wrote:
> >
> >> The nls_cp936.c is not synchronized with MS's translation table, there
On Sat, Jan 29, 2005 at 12:47:38PM -0500, Robert Love wrote:
> System calls are prefixed by "sys_". Thus, read(2) is implemented in
> the kernel as sys_read().
Now that you say this - of course you know that the actual
situation is much more messy. Sometimes I wonder whether
it would be useful t
On Fri, Jan 28, 2005 at 12:10:05PM +0100, Vojtech Pavlik wrote:
> And, btw, raw mode in 2.6 is not badly broken. It works as it is
> intended to. If you want the 2.4 behavior on x86, you just need to
> specify "atkbd.softraw=0" on the kernel command line.
Thanks for pointing that out - I should h
> > Only the ready flag was lost.
> No, note that if there was valid data we would see 0xa5 instead of
> 0x5a that was in the buffer - because in i8042_command we invert data
> coming from AUX port.
We misunderstand each other.
Let me repeat. The following happens:
We wait, then write d3, wait,
On Thu, Jan 27, 2005 at 10:09:24AM -0800, Linus Torvalds wrote:
> So what _might_ happen is that we write the command, and then
> i8042_wait_write() thinks that there is space to write the data
> immediately, and writes the data, but now the data got lost because the
> buffer was busy.
Hmm - I
On Thu, Jan 27, 2005 at 08:23:07AM +0200, Jaco Kroon wrote:
> i8042_check_aux: param_in=0x5a, command=AUX_LOOP, param_out=5a <= -1
> i8042_check_aux: param_in=??, command=AUX_TEST, param_out=a5 <= 0
The code is
param = 0x5a;
if (i8042_command(¶m, I8042_CMD_AUX_LOOP) || param != 0
Discussion:
Dmitry:
Here are patches with some delays. One never knows - maybe they
help someone.
Andries:
Only insert delays in the kernel source when either we know about
at least one person who reports that it helps, or about data sheets
that specify that the delay is required. Otherwise one c
On Thu, Jan 27, 2005 at 04:16:14AM +0100, Sasa Stevanovic wrote:
> I had some problems with my laptop's onetouch keys and it eventually led me
> to keyboard.c file from 2.6.10 kernel (Vojtech Pavlik and others). There
> may be a bug in the file, please read below.
>
> Well, actually, when all
On Tue, Jan 25, 2005 at 02:17:33PM -0500, Dmitry Torokhov wrote:
> Still, I wonder if implementing these delays will give IO controller
> better chances to react to our queries and will get rid of some
> failures.
My objection is this: by doing this you create myths that may
be difficult to dispe
On Tue, Jan 25, 2005 at 02:41:14AM -0500, Dmitry Torokhov wrote:
> Recently there was a patch from Alan regarding access timing violations
> in i8042. It made me curious as we only wait between accesses to status
> register but not data register. I peeked into FreeBSD code and they use
> delays to
On Mon, Jan 24, 2005 at 01:34:56AM +0100, Alessandro Sappia wrote:
> I was reading vt driver
> and I saw
> /*
> * To have permissions to do most of the vt ioctls, we either have
> * to be the owner of the tty, or have CAP_SYS_TTY_CONFIG.
> */
> perm = 0;
On Sun, Jan 23, 2005 at 11:56:28PM +0100, Wichert Akkerman wrote:
> > Are you still able to examine the situation?
>
> No, but I do have some more information. A e2fsck run on that filesystem
> was just as interesting:
>
> /dev/md4: clean, 16/132480 files, -15514/264960 blocks
>
> Forcing an e2
On Fri, Jan 21, 2005 at 03:11:06PM +0100, Wichert Akkerman wrote:
> After cleaning up a bit df suddenly showed interesting results:
>
> FilesystemSize Used Avail Use% Mounted on
> /dev/md4 1019M -64Z 1.1G 101% /tmp
>
> Filesystem 1K-blocks Used Available
On Thu, Jan 20, 2005 at 06:15:44PM +0100, Andrea Arcangeli wrote:
> > Yes, the fact that the oom-killer exists is a serious problem.
> > People work on trying to tune it, instead of just removing it.
>
> I'm working on fixing it, not just tuning it. The bugs in mainline
> aren't about the selecti
On Thu, Jan 20, 2005 at 12:00:34PM -0200, Marcelo Tosatti wrote:
> On Thu, Jan 20, 2005 at 02:15:56PM +0100, Andries Brouwer wrote:
> > Yes, the fact that the oom-killer exists is a serious problem.
> > People work on trying to tune it, instead of just removing it.
> >
>
On Thu, Jan 20, 2005 at 01:34:06PM +0100, Jens Axboe wrote:
> Using current BK on my x86-64 workstation, it went completely nuts today
> killing tasks left and right with oodles of free memory available.
Yes, the fact that the oom-killer exists is a serious problem.
People work on trying to tune
On Tue, Jan 18, 2005 at 05:35:48PM +0200, Jari Ruusu wrote:
> Fruhwirth Clemens wrote:
> > Nothing about kernel crypto is backdoored. If Ruusu thinks different, he
> > should show me source code. Till then, treat it as FUD.
>
> I have been submitting fix for this weakness to mainline mount (part o
On Tue, Jan 18, 2005 at 09:24:03AM -0500, Piszcz, Justin Michael wrote:
> Is the problem with the drive on the promise board or the drive on the
> VIA chipset?
Oh, please - no FUD. There is no problem, and we understand in detail
what happens and why it happens. There is no need for any speculati
On Tue, Jan 18, 2005 at 12:47:01PM +0100, Mario Holbe wrote:
> > If you want to restore the device to full size, use
> > blockdev --setbsz 512.
>
> Does that in any way hurt, if a filesystem is just mounted?
It is a bad idea to change the blocksize of a mounted filesystem.
-
To unsubscribe from
On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote:
> > I suppose that what happens is the following:
> > mounting sets the blocksize to 4096.
> > After reading 9992360 sectors, reading the next block means reading
> > the next 8 sectors and that fails because only 6 sectors are left.
On Mon, Jan 17, 2005 at 05:46:35PM -0200, Marcelo Tosatti wrote:
> On Sun, Jan 16, 2005 at 12:35:30AM +0100, Mario Holbe wrote:
> > mounting an ext2 (ext3 as well) filesystem seems to modify the
> > block device's EOF behaviour: before the mount the device returned
> > EOF, after the mount it does
On Mon, Jan 17, 2005 at 04:02:15PM -0800, Randy.Dunlap wrote:
> Al Viro wrote:
> >On Tue, Jan 18, 2005 at 02:54:24AM +, Daniel Drake wrote:
> >
> >>Retry up to 20 times if mounting the root device fails. This fixes
> >>booting
> >>from usb-storage devices, which no longer make their partition
On Tue, Jan 18, 2005 at 02:54:24AM +, Daniel Drake wrote:
> Retry up to 20 times if mounting the root device fails. This fixes booting
> from usb-storage devices, which no longer make their partitions immediately
> available.
>
> This should allow booting from root=/dev/sda1 and root=8:1 sty
> Date: Mon, 17 Jan 2005 03:21:30 -0800
> From: [EMAIL PROTECTED]
> Subject: [Bugme-new] [Bug 4054]
>
> Problem Description:
> Dane-elec 512MB USB keychain drive (using factory FAT partitions)
> works fine in windows, and on friend's 2.6.10-rc2-mm4 dual Athlon XP,
> but partition won't mount on my
On Sat, Jan 15, 2005 at 07:58:23PM -0800, Ulrich Drepper wrote:
> Matt Mackall wrote:
> >_Neither_ case mentions signals and the "and will return as many bytes
> >as requested" is clearly just a restatement of "does not have this
> >limit". Whoever copied this comment to the manpage was a bit slop
On Mon, Jan 10, 2005 at 08:49:09PM -0800, Andrew Morton wrote:
> Andries Brouwer <[EMAIL PROTECTED]> wrote:
> >
> > I wonder whether ps2esdi should be removed.
> > Does the present driver work for someone?
> > Have there been users in this millennium? With 2.
This evening I cleaned up sddr09.c, and after some playing
succeeded in writing to a SM card.
Remains the question: does anyone have docs for this thing?
(The "read control" command gives 64 bytes for each 16kB block.
The last 48 look like junk. The first 16 either are all zero,
or start with six
>> (a) It does less, namely will not kill processes with uid 0.
>> Ted, any objections?
Alan:
> That breaks the security guarantee. Suppose I use a setuid app to confuse
> you into doing something ?
On second thoughts I agree. Here is the patch without test for p->uid.
Andries
diff -u --recur
>> (a) It does less, namely will not kill processes with uid 0.
>> Ted, any objections?
Alan:
> That breaks the security guarantee. Suppose I use a setuid app to confuse
> you into doing something ?
You confuse me? Unlikely :-)
Indeed, discussion is possible. I think my version is more secure
Dear Linus, Alan, Ted, Andrew, all:
(i) Andrew - why don't you add yourself to the CREDITS file?
(then I'll find your email address at the first instead of the second attempt)
(ii) Yesterday I complained about the fact that pressing SAK twice
crashes the kernel (because the close from the first
I wanted to show someone how nice SAK works, pressed it twice,
and lo! it not only killed the processes on the console, but
also the kernel. Very effective.
The patch below (for a private, patched 2.4.3 - line numbers
may differ) diminish this effectiveness a little. My kernel
now survives.
Andr
Andre Hedrick wrote:
> That is a legacy bit from ATA-2 but it is one of those things you cannot
> get rid of :-(
in ANSI X3.279-1996, "AT Attachment Interface with Extensions (ATA-2)",
Approved September 11, 1996 , control register bit 3-7 are reserved.
However ANSI X3.2
> is it totally hopeless to want to try and get a USB keyboard to work
> as the systems only keyboard and have it work under X
> and also not freeze the whole system when hitting certain keys?
I just tried, and everything works flawlessly here [2.4.6pre5].
In case you see strange things for some
From: Andre Hedrick <[EMAIL PROTECTED]>
You know yourself first and all the screwed up ATAPI products that are
still using SFF-8020 that has been obsoleted before I start maintaining
the subsystem three plus years ago.
Hi Andre -
Why precisely is complying to SFF-8020 broken?
T
> Not that the documentation on MAP_ANON is any good either
> but at least the mere existence of the flag is mentioned.
> Seriously:
> both features ought to be documented in the man pages
> (I did submit a man page too, back in 1996)
Ah yes, I see. We both wrote a man page, and each contained
s
After sending util-linux out, I booted a kernel that had kdev_t
a pointer type, to see whether that still works.
And all (minus md/lvm/nfs that didnt compile) was fine
except that kswapd produced an oops. Investigation shows
that it was caused by the combination of what calls
"Ugly ugly ugly HACK
Just released: util-linux-2.11g
* MCONFIG & configure: fix for gcc 3.0
Note that nfsmount_xdr.c may give warnings with gcc 3.0, essentially
because of defines in that use things like ntohl(*buf++)
where ntohl(x) is a macro with several occurrences of x.
* blockdev: support for the get/set
Rogier Wolff writes:
>> But why 1024?
>> (Or make the set blocksize ioctl also work on loop devices.)
> I thought the change was a "quick hack" that would make stuff work
> (page cache?) near the end of the file. That would mean that this kind
> of "quick hack" won't work.
I am not sure I can
From [EMAIL PROTECTED] Tue Jun 26 10:20:51 2001
This patch fixes the problem. Please consider applying.
--- linux-2.4.6-pre5/drivers/block/loop.cSat Jun 23 07:52:39 2001
+++ linux/drivers/block/loop.cTue Jun 26 09:21:47 2001
@@ -653,7 +653,7 @@
bs = 0;
Why does the console ioctl, KDSKBLED, work with
caps and num lock, but not scroll lock.
...
But "setleds +scroll" changes the scroll lock led without
changing the behavior of the keyboard. I then have to press
the scoll lock key twice to get the scroll lock light to turn o
From: Jari Ruusu <[EMAIL PROTECTED]>
File backed loop device on 4k block size ext2 filesystem:
# dd if=/dev/zero of=file1 bs=1024 count=10
10+0 records in
10+0 records out
# losetup /dev/loop0 file1
# dd if=/dev/zero of=/dev/loop0 bs=1024 count=10 conv=notrunc
dd:
> No comments on races, but there's obvious one on API: doing that on
> per-major basis is _wrong_.
Even though you do not define "that", most likely I agree.
Still, many intermediate steps are needed.
For a very large number of these steps the final API is irrelevant.
The project of this week i
An hour ago or so I put 07-2.4.6pre5-gendisk on ftp.kernel.org
(and rediffed the previous six patches against 2.4.6pre5).
It has add_gendisk, del_gendisk, get_gendisk, blk_gendisk[]
(a.k.a. register_gendisk, unregister_gendisk, find_gendisk),
so that one now can find the gendisk structure given a
> Is it worth keeping these so we can build things like nice
> /proc files or use them later ?
Some, rather different, form will come back.
For now I would prefer throwing out as much as possible.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
> We will need register_disk().
> Reinserting it into the right places in 2.5 is a unnecessary PITA.
(i) today this is dead code
(ii) I am slowly restructuring all blockdev code, mainly with
the purpose of freeing partition code from the bowels of the
various drivers. In the process register_disk
In fs/partitions/check.c we read
void register_disk(struct gendisk *gdev, kdev_t dev, unsigned minors,
struct block_device_operations *ops, long size)
{
if (!gdev)
return;
grok_partitions(gdev, MINOR(dev)>>gdev->minor_shift, minors, size);
}
showing that r
On ftp.kernel.org under kernel/people/aeb two files
03-2.4.6pre3-remove-real_devices and 04-2.4.6pre3-remove-max_p
that remove the fields real_devices and max_p from a struct gendisk
(and initialize such structs with the field: syntax).
The patches could be applied today, except that probably the
> setuid(2) differs from the OpenBSD setuid(2)
> Either I am non compos or the thing is very wrong.
> The docs (man-pages-1.35) say ...
Yes, setuid() has a behaviour that varies a bit from system to system.
Moreover, it has varied in the history of Linux. The manpage may have
been correct when it
> how do the inode->i_dev, i_rdev fit into this?
These are what you see with stat(2).
i_dev gives the device the file is on
i_rdev is usually undefined, but for device special files
it gives the real device.
> Is there a set rule on when/where one should use a buffer head's
> b_dev and when/wher
Moving the "partition shift"
block += partition_start;
from the bowels of SCSI and IDE drivers to ll_rw_blk.c
(something that must wait for 2.5) I changed sd_init a bit
and noticed that the present version is buggy:
static struct gendisk sd_gendisk = {
SCSI_DISK0_MAJOR, /* M
1 - 100 of 393 matches
Mail list logo
