On Mon, 28 Sep 2020 at 09:29, Dmitry Vyukov wrote:
> On Mon, Sep 28, 2020 at 10:23 AM Tigran Aivazian
> > No, this is not an issue. In the latest change to BFS I added the
> > following comment to the header fs/bfs/bfs.h, which explains it:
> >
> > /* In theory BF
d with such "impossible to fill up" number
of inodes */
Kind regards,
Tigran
I see no problems for BFS.
Acked-By: Tigran Aivazian
Hi Greg,
Thanks for pushing this into sable as well. However, I think patch makes more
sense
with 320f35b7bf8cccf1997ca3126843535e1b95e9c4
Tigran.
- Original Message -
> From: "Greg Kroah-Hartman"
> To: "linux-kernel"
> Cc: "Greg Kroah-Hartman&
Hi Greg,
Thanks for pushing this into sable as well. However, I think patch makes more
sense
with 320f35b7bf8cccf1997ca3126843535e1b95e9c4
Tigran.
- Original Message -
> From: "Greg Kroah-Hartman"
> To: linux-kernel@vger.kernel.org
> Cc: "Greg Kroah-Hartman&
Re-sending the patches with the "Cc: sta...@vger.kernel.org" included
in the sign-off area, as per Option 1 of the rules Greg referred me
to. I hope that now I have done everything by the rules.
On Sun, 2 Dec 2018 at 21:42, Tigran Aivazian wrote:
>
> just wanted to add: although
just wanted to add: although the subject says "4.19.6" the patches
apply perfectly to the top of "torvalds/linux" tree from github.
On Sun, 2 Dec 2018 at 21:01, Tigran Aivazian wrote:
>
> Hi Linus,
>
> I attached two incremental patches for BFS:
>
> 1. Make i
Hi Linus,
I attached two incremental patches for BFS:
1. Make inode bitmap allocation static (applies on top of 4.19.6)
2. Strengthen the superblock sanity checking code (applies on top of 1. above)
Kind regards,
Tigran
From: Tigran Aivazian
Subject: [PATCH 4.19.6 1/2] BFS updates
Make in
quot;-mm" tree and then into "linux-next" tree.
I am happy to split it into multiple logical patches and send them to
Linus, of course.
Kind regards,
Tigran
tested under 4.19.6 kernel.
Kind regards,
Tigran
From: Tigran Aivazian
Subject: [PATCH 4.19.6] BFS: static inode bitmap and extra sanity checking
Strengthen validation of BFS superblock against corruption.
Make in-core inode bitmap static part of superblock info structure.
Print a warning when
opment, I presume the basic
fundamental fact that no patch is accepted if the relevant maintainer
has objections to it is still intact. And I am both the author and the
maintainer of the BFS filesystem.
Kind regards,
Tigran
On Thu, 29 Nov 2018 at 16:07, Greg KH wrote:
> On Thu, Nov 29, 2018 at 03:23:00PM +0000, Tigran Aivazian wrote:
> > Yes, of course I object to it.
> I can not apply a patch to the stable trees that are not in Linus's tree
> first. So there's nothing I can do here wi
4.20 was applied (as "linux-next", I don't know why it
is not in 4.20-rc4 yet), but 4.19.2 version was not applied yet, so
here it is attached again (with the proper changelog etc). It applies
to 4.19.5 cleanly as well, so please use this version (attached).
Kind regards,
Tigran
On T
On Thu, 22 Nov 2018 at 19:42, Sasha Levin wrote:
> Hm, but this one is not upstream yet? I'll wait with it until it gets
> some time to soak upstream.
It is in linux-next, so I assume it will propagate to the numbered
releases soon, see here:
https://git.kernel.org/pub/scm/linux/kernel/git/next/l
ot;Signed-off-by:" line and diffstat output. And now I've also cc'd the
linux-kernel mailing list.
Kind regards,
Tigran
From: Tigran Aivazian
Subject: bfs: extra sanity checking and static inode bitmap
Strengthen validation of BFS superblock against corruption.
Make in-core inode b
On Tue, 13 Nov 2018 at 19:40, Tigran Aivazian wrote:
>
> On Tue, 13 Nov 2018 at 08:31, Tigran Aivazian
> wrote:
> > Andrew, if you would like me to make the same patch against 4.19.1 as
> > well, please let me know.
>
> I decided to just go ahead and backport it to 4.
On Tue, 13 Nov 2018 at 08:31, Tigran Aivazian wrote:
> Andrew, if you would like me to make the same patch against 4.19.1 as
> well, please let me know.
I decided to just go ahead and backport it to 4.19.1 anyway (see
attached). Tested thoroughly under 4.19.1.
From: Tigran Aivazian
Subjec
heck) patch to
Andrew Morton a couple of days ago against 4.20-rc1.
Andrew, if you would like me to make the same patch against 4.19.1 as
well, please let me know.
Kind regards,
Tigran
>
> Link:
> http://lkml.kernel.org/r/1525862104-3407-1-git-send-email-penguin-ker...@i-love.sak
Hi Borislav,
Ok, that's fine. I noticed these things when changing BFS code a
couple of days ago and wondered what they were --- now I know :)
Kind regards,
Tigran
On Fri, 9 Nov 2018 at 15:04, Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> ... and drop the GPL v2
Hi Andrew,
Here is the detailed information about the bug which Tomas fixed. As
for the word-wrapping --- I enabled "plain text mode" in Gmail.
However, just in case, I am sending the combined patch as a text file
attachment. Is this ok?
Kind regards,
Tigran
On 15 June 2018 at 19
OWARN and printf().
>
> [1]
> https://syzkaller.appspot.com/bug?id=16a87c236b951351374a84c8a32f40edbc034e96
>
> Signed-off-by: Tetsuo Handa
> Reported-by: syzbot
> Cc: Tigran A. Aivazian
> ---
> fs/bfs/inode.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-
Hi,
If you had created the filesystem with the proper mkfs under SCO
UnixWare 7 you (probably) wouldn't encounter this issue. But since
commercial Unix-es are now part of history and the only proper way is
the Linux mkfs.bfs utility, your patch is fine.
Kind regards,
Tigran
On 5 May 2017
Dear stable kernel maintainers,
Please consider commit
f17f8a14e82cdf34cd6473e3644f3c672b3884f6
to be included into 4.10 kernel. As long as it crashes
kernels used by some distors, we have to disable corresponding
functionality on the NFS servers.
Thanks in advance,
Tigran.
Hi Joe,
I would suggest that those addresses which bounce should certainly be
removed, but the rest should be left alone.
Kind regards,
Tigran
PS. Joe, sorry if you received this message twice --- my first attempt
to reply failed because gmail used html by default :)
On 25 August 2016 at 00:33
ded to use MDS
Thanks,
Tigran.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
clutch = joyInfo->ax[cmd[CMD_CLUTCH].val];
// dirty stuff, sorry
if (clutch <= 0) clutch = -clutch;
else clutch = 2.0 - clutch;
clutch /= 2.0;
car->_clutchCmd = fa
hings like
that, which are best left to the author of the code to decide which
declaration should be where?
Kind regards
Tigran
*);
+
Functions should not be externed, remove extern keyword.
why not?
In (roughly, because ^extern pattern is not ideal) 3959 cases only in
include/linux/*h they are:
$ grep ^extern include/linux/*h | wc -l
3959
Kind regards
Tigran
--
To unsubscribe from this list: send the line
Ooops, I didn't look at the _name_ of the function, i.e. it being
dump_imap(), an internal helper --- of course it shouldn't be extern'd you
are right :)
On Thu, 24 Jan 2008, Tigran Aivazian wrote:
On Fri, 25 Jan 2008, Heikki Orsila wrote:
On Fri, Jan 25, 2008 at 01:32:04A
/lib/modules).
I cc'd linux-kernel as someone may wish to fix this. (see below for the
actual report).
Kind regards
Tigran
On Sun, 14 Jan 2007, Tigran Aivazian wrote:
I forgot to mention that on another machine running the same kernel version
with the same (as close as a UP machine
nside #ifdef
CONFIG_HOTPLUG_CPU.
Kind regards
Tigran
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
driver isn't declared __cpuinitdata...
But to tidy up one should add __cpuinitdata as you suggest (to guard for
the case if these two slip out of CONFIG_HOTPLUG_CPU, although they are
meaningless if cpu hotplug support is not configured in).
Kind regards
Tigran
On Sun, 17 Dec 2006, Jean De
Hi Andrew,
As Adrian pointed out recently, there were still a couple of places where
I should have fixed my email address. The patch is attached (as attachment
so as to not let pine corrupt it).
The patch is against 2.6.19.1.
Kind regards
Tigran--- arch/i386/kernel/microcode.c.0 2006
I see Alan Cox already replied and I
agree with both you and Alan on this.
Kind regards
Tigran
-
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.org/majordomo-info.html
Pl
me? Start with the top --- Linus Torvalds :) Try finding an
obsolete email address for him in the kernel. By 2030 my turn may come :)
Kind regards
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
--- I only saw it now via lkml archive.
Kind regards
Tigran
On Fri, 1 Dec 2006, Adrian Bunk wrote:
On Fri, Dec 01, 2006 at 10:08:39AM +0100, Arjan van de Ven wrote:
On Thu, 2006-11-30 at 22:00 -0800, Hua Zhong wrote:
I am curious, what's the point?
These email addresses serve a "
ree, so I should have included in the patch the change to
MODULE_AUTHOR (in both microcode and bfs).
Or maybe MODULE_AUTHOR shouldn't contain the email address, if the module
is mentioned in the MAINTAINERS which does contain it? Why repeat the data
and so have to remember to main
Sorry, it was a "red herring", namely my module's Makefile still had
"-mregparm=0" in CFLAGS, so that is why kdb showed it's arguments
correctly (and then paniced on the way out).
So we still have to deal with DWARF2 data then... Ok, will look into it.
Kind rega
On Tue, 18 Jan 2005, Tigran Aivazian wrote:
I already solved this paricular problem. And the solution is (but don't tell
me you knew it, for then why didn't you tell anyone) simply --- compile the
kernel with -g and that includes enough debug information to be able to
decode the sta
must never compile the kernel
with -g either...)
Kind regards
Tigran
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
t the "magic stuff" which gdb does is in fact a dwarf2
implementation (and this is what's missing in kdb on x86_64).
Kind regards
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo i
us.
Please don't apply this, it was especially intended for modular debuggers.
There is already a hacvked kdb around that uses it.
eh didn't Tigran just mail lkml claiming that kdb and x86-64 really
don't mix ??
No, I emailed saying that kdb on x86_64 does NOT show the values of
param
ce and actively
maintained piece of work, so it should be fixed to show the parameter
values correctly in the backtrace.
Kind regards
Tigran
-
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://
e these frames correctly, right?
I just want someone who knows the answer to confirm the last statement and
so then I can go ahead and (try to) implement the solution by mimicking
gdb behaviour (or help Jack Vogel implement it if he prefers doing it
himself as defacto kdb/x86_64 maintainer)
K
Hi Sathish,
The function of getname() is to allocate some (kernel-space) memory for
the userspace-passed filename and copy it from user space to kernel space.
Regards,
Tigran
On Mon, 18 Jun 2001, SATHISH.J wrote:
> Hi,
>
> Sorry if this question is too silly.
>
> I could not
it is
stripped of extra (unnecessary, imho) logic and turned into a plain one I
suggested above.
Regards,
Tigran
-
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.org/majordomo-
ux/dcache.h"
This assumes you have built the tags by:
# cd /usr/src/linux
# find -name '*.[ch]' | ctags -L- &
# echo "set tags=tags" >> .vimrc
And, btw, it is a static inline, not a function per se.
Regards,
Tigran
-
To unsubscribe from this list: send the li
t you objected and that is fine, but at
least making it optionally possible would be _very nice_, please.
Regards,
Tigran
-
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.kern
far beyond the bounds of IA32
architecture -- it is portable, flexible and, in one word, perfect :)
Regards,
Tigran
On Mon, 2 Apr 2001, Wolfgang Rohdewald wrote:
> in 2.2.19, linux/include/asm-i386/uaccess.h is missing the line
>
> #define strlen_user(str) strnlen_user(str, ~0UL >>
urnalling filesystem etc...
Regards,
Tigran
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
l stop here/now but I will definitely come back to this interesting
problem in 24 hours. But if anyone fixes it before then, I won't cry :)
Of course, before sending anything I will make sure my patch works on
_all_ my machines without any exceptions.
Regards,
Tigran
-
To unsubscrib
quot; in
the code) then they should remain constant when one is overclocking,
right?
As for my question on the evenness of the calls to identify_cpu() --
ignore it, it was obvious, of course (called from check_bugs() on
boot_cpu_data and then on SMP on each cpu_data + id)
Regards,
Tigran
-
To
(KERN_ERR "lo=%x hi=%x\n", lo, hi);
produces the output:
# dmesg | grep lo=
lo=c5100800 hi=0
lo=c5100800 hi=0
lo=c5000800 hi=0
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo in
On Fri, 2 Mar 2001, Ingo Molnar wrote:
> > + if (c == &misc_list) {
> >
> > This should be (c != &misc_list)
>
oops, I didn't notice -- ignore the patch I sent a minute ago :)
Regards,
Tigran
-
To unsubscribe from this list: send the line "uns
On Fri, 2 Mar 2001, Tigran Aivazian wrote:
> On Thu, 1 Mar 2001, Alan Cox wrote:
> > 2.4.2-ac8
> > o Stop two people claiming the same misc dev id (Philipp Rumpf)
>
> is this what has broken misc devi registration on my machine? I have two
> misc devices -- microcode
ot gpm generates an "oops" from gpm.c(968) saying
"/dev/mouse: No such device"
So, ac8 has two problems for me:
1. /proc/cpuinfo shows wrong info about bus (claims to be overclocked) --
I will get back to you with the info you requested shortly
2. misc device registration is broke
o with misc device registration as
I lost not just psaux but microcode device (which happens to be misc as
well)
Regards,
Tigran
-
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.kern
On Thu, 1 Mar 2001, José Luis Domingo López wrote:
> Linux 2.4.2-ac7 reports wrong CPU speed and model name for a Pentium III
> correctly detected on, at least, 2.2.18, 2.4.2 and 2.4.2-ac4. The
> processor is a 600 MHz one, with a 133 MHz front bus.
same here with PIII550MHz/100MHz bus. Actually,
ted to without breaking any userland.
Regards,
Tigran
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
use it is illegal (without
going through proper steps of publishing them), I shouldn't even be saying
that they show Linux to be much faster :)
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECT
- why not
consider it sooner rather than later?
Regards,
Tigran
diff -urN -X dontdiff linux/drivers/char/raw.c vmfs/drivers/char/raw.c
--- linux/drivers/char/raw.cMon Oct 2 04:35:15 2000
+++ vmfs/drivers/char/raw.c Thu Feb 22 07:21:26 2001
@@ -277,8 +277,11 @@
if ((
play with this and see if it detects my ISA-PNP SB
AWE64 card. Give the above patch a try and see if you figure out the
values to plug in there sooner than I do.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
back ?
>
when you compile your 2.4.x kernel make sure you set the "4G of RAM"
option, i.e. CONFIG_HIGHMEM4G. If you chose "up to 1G" then it means "up
to 986M" (or something like that) -- the number in Help is just rounded up
to confuse the dummy user :)
Re
yes, just run the famous mptable program. If the machine is SMP then it
will have a valid Intel MP 1.4 configuration tables so the program will
show meaningful output.
Regards,
Tigran
On Tue, 20 Feb 2001, Burton Windle wrote:
> Hello. Is there a way, when running a non-SMP kernel, to detect
On Wed, 21 Feb 2001, Jeff Garzik wrote:
> On Wed, 21 Feb 2001, Tigran Aivazian wrote:
> > yes, just run the famous mptable program. If the machine is SMP then it
> > will have a valid Intel MP 1.4 configuration tables so the program will
> > show meaningful output.
>
On Wed, 21 Feb 2001, Tigran Aivazian wrote:
> yes, just run the famous mptable program.
before I am snowed under with questions about where to get this program,
here is the src and binaries that I use -- it is quite possible that there
is a newer version (I suspect Ingo Molnar might know bet
On Wed, 21 Feb 2001, Tigran Aivazian wrote:
> On Wed, 21 Feb 2001, Giuliano Pochini wrote:
>
> >
> > Perhaps this is a faq...
> > I have a dual-800 (mb asus, no AGP) with 1GB ram,
> > but according to /proc/meminfo tells I only have
> > 90KB. I tri
e like
David Parsons will probably be interested in your configuration...
Regards,
Tigran
-
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.org/majordomo-info.html
Please read
ry big) ext2 filesystem with 0
processes killed.
The kernel I use is 2.4.2-pre3. The machine has 6G RAM with the 3G given
to kernel virtual. The amount of swap is massive (2G) but it is never
used.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
e to find bugs in them and _mandate_
that I accept the fixes (if they are correct) -- I have no right to
neglect them.
Regards,
Tigran
-
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
een some people setting this TASK_RUNNING incorrectly, based on a
mere observation that "official Linux kernel code does so" -- so the patch
below is not just an optimization but serves for education (i.e. to stop
people copying unnecessary code).
Regards,
Tigran
PS. Btw, I still haven&#x
uot;) and create a pipe, just use shell
input redirection facility "<".
Regards,
Tigran
On Tue, 13 Feb 2001, Thomas Foerster wrote:
> Hi folks,
>
> sorry for the silly question, but i can't get it to work :
>
> I have linux-2.4.1 unpacked, configured and install
counting to ten lately?
>
yes, my fingers are okay -- I frequently check the mapping between the
items in Exodus 20 and the fingers to make sure I still have the right
number (of both).
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
suspicious.
Regards,
Tigran
On Tue, 13 Feb 2001, Alan Cox wrote:
> > > When you say 2.2.x works does that include 2.2.18.
> >
> > no, I meant the plain 2.2.x as of Red Hat 7.0 which is labelled as
> > "2.2.16-22".
>
> Can you try 2.2.18/2.2.19pre. T
s email about was -- I get the same
effect licq (just lost "in" before licq!) so it is not xterm-specific but
probably that is not importt anymore (just lost "an" in
"important").. (lost a . in "..." :)
Tgran (unbelievable -- it doesn't even let me spell
d, nor APM in the kernel.
Regards,
Tigran
On Tue, 13 Feb 2001, Andrew Morton wrote:
> Hi, Tigran.
>
> Internal keyboard, or external?
>
> Does it happen on the console or just in X? (How come you can't
> tell whether it's the k/b driver or the PTY driver?)
>
>
.4 handle keyboard error cases quite differently (less so as of 2.2.18)
> When you say 2.2.x works does that include 2.2.18.
no, I meant the plain 2.2.x as of Red Hat 7.0 which is labelled as
"2.2.16-22".
>
> The next stage then is probably to log when you see errored keyboard byte
On Tue, 13 Feb 2001, Tigran Aivazian wrote:
>
> PPS. No, my laptop is fine -- rebootingnto 2.2.x makes it type without
> loosing characters...
>
just to clarify -- it does _not_ add characters -- the "loosing" vs
"losing" thing is my own frequent typo :)
Ti
k fine previously -- like in the days
of 2.3.99 and 2.4.0-teX series (yes, teX was meant to be "testX"!)
So, the keyboard or pty driver is badly broken.
Regards,
Tigran
PS. This only happens on this Dell latitude CPx (notice lost shift in
Latitude?) H450GT.
PPS. No, my laptop is fine -
hange ig you stay within i386 architecture). It is available to
programs by including header.
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Doug,
I confirm that ac7 fixed all the aic7xxx problems on my machine.
Thanks,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
two mistakes:
a) [EMAIL PROTECTED], not veritas.com! (it was pine, not me -- default
domain etc :)
b) it was ac6 which fixed it, not ac7 (but I am running ac7)
On Thu, 8 Feb 2001, Tigran Aivazian wrote:
> Doug,
>
> I confirm that ac7 fixed all the aic7xxx problems on my machine.
&g
Error detected
(scsi0) SEQADDR=0x58
Kernel panic: aic7xxx: unrecoverable BRKADRINT
The Linux 2.4.2-pre1 works fine. Next thing I was thinking was to try ac4
and also to try on a different machine which has a different revision of
the same type of aic7xxx HBA.
Any more ideas?
Regards,
Tigran
-
To
-13048: reiserfs_iget: bad_inode. Stat data of (0 1) not found
and the run aborts.
Any clues?
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
and, while you are at it, you should (probably) also mark pin_2_irq() and
IO_APIC_get_PCI_irq_vector() functions as __init as well, for exactly the
same reason as what you noticed.
Regards,
Tigran
On Mon, 5 Feb 2001, Dunlap, Randy wrote:
> Hi,
>
> Just a question (not a patch
On Mon, 5 Feb 2001, Tigran Aivazian wrote:
> Basically, I badly needed to be able to build kernels of arbitrary size
not just "to build", but "to boot", of course :)
Also, while we are in a history lesson, I might as well add that this was
precisely the time when h
tural that one should printf a warning.
So, in short, such kernels are okay to boot with LILO (and most other
bootloaders) but not if you just dd if=bzImage of=/dev/fd0, i.e. not by
bootsect.S
If you want the date... it was approximately the beginning of 2000, I
think.
Regards,
Tigran
ok, since so many people ask for it to be called "rootfstype=", I will do
so and resend the patch.
Any other comments? I think on the last round I have incorporated all the
comments (except the "rootfs" -> "rootfstype" one)...
Tigran
On Mon, 5 Feb 2001, We
ad another
filesystem made on it if it's superblock is left intact.
Regards,
Tigran
diff -urN -X ../dontdiff linux/Documentation/kernel-parameters.txt
rootfs/Documentation/kernel-parameters.txt
--- linux/Documentation/kernel-parameters.txt Sat Dec 30 19:23:13 2000
+++ rootfs/Documentation/kernel
whole brelse()
could just contain a single atomic_dec() and that is all.
Regards,
Tigran
PS. Having thought about it -- it was neither sct, nor Alan, nor even
Andrea -- it was Linus who explained it :)
On Fri, 2 Feb 2001, Daniel Phillips wrote:
> There is a rare SMP race in brelse:
>
SFS
benchmark suite)?
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
ly". (for this to work in practice you would need to
instruct the editor of the suitable buffer sizes or to furnish the driver
with a huge amount of extra logic to accumulate the chunks received of any
size into appropriate ones).
So, in short, no, your patch is of no use, thank you.
Regards,
Tigran
On Tue, 23 Jan 2001, Tigran Aivazian wrote:
> So, since kdb was unable to tell me what's going on (and truss also can't
> attach to it) one will have to debug it the old-fashioned way -- manually,
> i.e. by trussing klogd from the beginning and reading it's sources...
act
edit /etc/rc.d/init.d/syslog. This is very similar to
what one has to do if he wants to use NFSv3 client/server and latest
nfsutils on Red Hat systems (they are broken by default)
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
On 23 Jan 2001, Chmouel Boudjnah wrote:
> Tigran Aivazian <[EMAIL PROTECTED]> writes:
>
> > Btw, this only happens on my laptop and not on the desktop. It only
> > happens _after_ some activity but I have not yet managed to narrow down
> > exactly what activity.
&
nd not on the desktop. It only
happens _after_ some activity but I have not yet managed to narrow down
exactly what activity.
Regards,
Tigran
PS. No, I don't use power management or anything fancy/unproven like that
-- laptop is just a small/portable desktop, imho.
-
To unsubscribe from this lis
On Tue, 16 Jan 2001, Tigran Aivazian wrote:
> Fixing this requires either a new filesystem type (drifs) or
> (simpler!) redesigning dri to separate common things into a separate
> dri_core thing shared amongst them.
just for completeness -- there is the 3rd option -- one could just fix
ixing this requires either a new filesystem type (drifs) or
(simpler!) redesigning dri to separate common things into a separate
dri_core thing shared amongst them.
Regards,
Tigran
On Tue, 16 Jan 2001, Bobo Rajec wrote:
>
> Hi,
>
> I'm running kernel 2.4.0 on Redhat 7.0. I trie
Ware 7.1.1+ -- this would be a very useful exercise as I
vaguely remember some people claiming that Linux PAE implementation is
not ideal (if it is true then it ought to be made ideal to be inline with
the rest of the kernel).
Regards,
Tigran
-
To unsubscribe from this list: send the line "u
Hi Alan,
I sent this one-liner to Linus ages ago but he didn't notice it. The bug
is obvious -- the goal of microcode_init() is to succeed at least in one
of either devfs or misc registration.
Regards,
Tigran
--- linux/arch/i386/kernel/microcode.c Mon Dec 11 21:42:08 2000
+++ work/arch
1 - 100 of 428 matches
Mail list logo
