On Sun, 17 Jun 2001, Matt Dillon wrote:
> Ok, this patch should do it. For review. I've made it return ENOENT,
> which is the same error that is returned when you try to open an empty
> path (e.g. open("", ...)).
>
> (Note: This is unrelated to Bruce's second issue with 'cp' co
> On Mon, 04 Jun 2001 19:20:36 +0900 (JST),
> Hajimu UMEMOTO <[EMAIL PROTECTED]> said:
> I just put the patch for merging latest KAME into FreeBSD:
> http://www.imasy.or.jp/~ume/ipv6/test/freebsd5-kame20010528-20010604.diff.gz
> This is based on KAME snap 20010528 and against 5-CURREN
Heh. We came up with virtually the same patch at the same time!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, Jun 18, 2001 at 03:40:28 +0200, Assar Westerlund wrote:
>
> What about this?
>
Matt's variant is better because return ENOENT _before_ NAMETOOLONG check.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the b
:
:On Sun, Jun 17, 2001 at 21:16:24 -0400, Garance A Drosihn wrote:
:>
:> When I say this, I assume that the only change to make is how any
:> 'open' or 'stat' call will handle null symlinks. If I am reading
:> Andrey correctly, there will be no change to the 'ln' command or
:> the symlink() sy
Garance A Drosihn <[EMAIL PROTECTED]> writes:
> I think that it's reasonable to just make it a specific error, and
> thus end this thread. No harm will come of making it a specific
> error on open, and it will address the problems mentioned earlier.
What about this?
/assar
Index: vfs_lookup.c
On Sun, Jun 17, 2001 at 21:16:24 -0400, Garance A Drosihn wrote:
>
> When I say this, I assume that the only change to make is how any
> 'open' or 'stat' call will handle null symlinks. If I am reading
> Andrey correctly, there will be no change to the 'ln' command or
> the symlink() system rout
Garrett Wollman <[EMAIL PROTECTED]> writes:
> < said:
>
> > telnet* should never have used libmp in the first place,
>
> Yes, it should have, since telnet is historic BSD software and libmp
> is the historic BSD arbitrary-precision-math library.
But telnet in historic BSD didn't have sra or any
On Sun, Jun 17, 2001 at 18:00:06 -0700, Matt Dillon wrote:
>
> I think we can safely disallow path lookups going through empty symlinks
> (i.e. at the time of the open(), lstat(), etc...), but we should not
> go changing the "ln" command or the symlink() system call.
This is exact t
At 2:28 PM -0700 6/17/01, Matt Dillon wrote:
>:On Sun, Jun 17, 2001 at 11:31:41 -0700, Jordan Hubbard wrote:
>:> It seems your argument to disallow null symlinks got somehow taken
>:> as an argument to disallow all "invalid" symlinks then.
>:
>:
>:To say it more clear: now I even not against ""-sy
< said:
> telnet* should never have used libmp in the first place,
Yes, it should have, since telnet is historic BSD software and libmp
is the historic BSD arbitrary-precision-math library. That is also
(one reason) why we should continue to supply a libmp, regardless of
what code it is actuall
:There is nothing to fix. Sometimes 'make install' instead 'make
:installworld' typed can produce this. Of course, install procedure can be
:complicated to make it foolprof, but I think the system must be fixed
:instead to not resolve illegal names. It is not good idea to
:produce workarounds of
Commenting out hint.atkbd.0.* and hint.psm.0.* fixed the problem that
others reported.
Little investigation showed that the new resource_find() function in
kern/subr_bus.c finds two atkbd0 and two psm0, one of each from
kern_envp, and the other one from static_hints; no wildcard matches
were inv
On Sun, Jun 17, 2001 at 17:26:16 -0700, Matt Dillon wrote:
>
> If something in the build is creating empty symlinks under certain
> circumstances, that something should be fixed. The problem isn't ln -s.
There is nothing to fix. Sometimes 'make install' instead 'make
installworld' typed
On Sun, Jun 17, 2001 at 17:01:08 -0700, Matt Dillon wrote:
> I'm sorry, I don't understand... what does this have to do with
> an empty symlink verses a symlink containing something else?
> 'rm' does not traverse symlinks.
I not mean 'rm' literally.
Read Bruce's comment about how fake
>Date: Mon, 18 Jun 2001 00:33:18 +0200
>From: Philipp Mergenthaler <[EMAIL PROTECTED]>
>Revision 1.39 of dsp.c doesn't fix this panic.
1.40 (along with associated changes to sndstat.c, sound.c, & sound.h)
appears to work OK for me -- thanks!
(Hmmm... I just noticed another round of changes
:
:On Sun, Jun 17, 2001 at 15:04:06 -0700, Matt Dillon wrote:
:>
:> What cases? In all my years of programming I've never once 'accidently'
:> created an empty symlink.
:
:See initial Bruce comments. Sometimes when 'make hierarchy' step is
:missing, intermediate result of 'make install'
:
:On Sun, Jun 17, 2001 at 15:04:06 -0700, Matt Dillon wrote:
:> What cases? In all my years of programming I've never once 'accidently'
:> created an empty symlink.
:
:The next example is fts-like activity - wrong final destination
:appearse which is dangerous for 'rm'. I.e. in some sit
On Sun, Jun 17, 2001 at 15:04:06 -0700, Matt Dillon wrote:
> What cases? In all my years of programming I've never once 'accidently'
> created an empty symlink.
The next example is fts-like activity - wrong final destination
appearse which is dangerous for 'rm'. I.e. in some situation yo
On Sun, Jun 17, 2001 at 15:04:06 -0700, Matt Dillon wrote:
>
> What cases? In all my years of programming I've never once 'accidently'
> created an empty symlink.
See initial Bruce comments. Sometimes when 'make hierarchy' step is
missing, intermediate result of 'make install' can't be
:On Sun, Jun 17, 2001 at 14:28:40 -0700, Matt Dillon wrote:
:
:> rather then trying to resolve it. I'm not sure it's worth it, though.
:> It just doesn't come up that often and there are a thousand other ways you
:> can hogtie yourself in the system that takes less effort.
:
:It wort
On Sun, Jun 17, 2001 at 01:51:56PM -0700, Kris Kennaway wrote:
> libbn is already part of OpenSSH; it's a trivial matter to make it
> into a standalone library. In other words, we already include two
> functionally equivalent bignum libraries in FreeBSD, so one of them
> should go.
I couldn't a
On Sun, Jun 17, 2001 at 14:28:40 -0700, Matt Dillon wrote:
> rather then trying to resolve it. I'm not sure it's worth it, though.
> It just doesn't come up that often and there are a thousand other ways you
> can hogtie yourself in the system that takes less effort.
It worth. It ca
:On Sun, Jun 17, 2001 at 11:31:41 -0700, Jordan Hubbard wrote:
:> It seems your argument to disallow null symlinks got somehow taken
:> as an argument to disallow all "invalid" symlinks then.
:
:
:To say it more clear: now I even not against ""-symlinks making ability,
:such strings are valid per
On Sun, Jun 17, 2001 at 06:22:56PM +0300, Giorgos Keramidas wrote:
> On Sat, Jun 16, 2001 at 11:38:45PM -0700, Peter Wemm wrote:
>
> > It should not be too hard to have build a lightweight 'libbignum' that
> > is extracted from the openssl sources and make that available in the base
> > system.
On Sun, Jun 17, 2001 at 12:49:34PM -0700, David Wolfskill wrote:
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0xc
> fault code= supervisor read, page not present
> instruction pointer = 0x8:0xc018fe1a
> stack pointer = 0x10:0xce5a4d40
> frame poi
>Date: Sun, 17 Jun 2001 12:49:34 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
[Yes, I *do* talk (well, mumble) to myself dhw]
>Now, back on 13 June, I had added another line to /etc/rc.devfs -- the
>line symlinking /dev/dsp0 to /dev/dsp; here are the lines I've added:
># Setup DEV
OK; this is a(nother) "page fault while in kernel mode," but I suspect
it's one I hadn't seen mentioned yet. The "good news" is that it is
eminently reproducible. :-} Also, I was able to boot kernel.old OK, so
hat should decrease the probability that the problem is (strictly)
somewhere in userl
On Sun, Jun 17, 2001 at 11:31:41 -0700, Jordan Hubbard wrote:
> It seems your argument to disallow null symlinks got somehow taken
> as an argument to disallow all "invalid" symlinks then.
To say it more clear: now I even not against ""-symlinks making ability,
such strings are valid per POSIX a
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Dima Dorfman writes:
> >Jens Schweikhardt <[EMAIL PROTECTED]> writes:
> >> hello, world\n
> >>
> >> with a system cvsupped June 6th I can reliably reproduce a
> >> [panic]
> >> when I try to unmount a deleted mdconfig
It seems your argument to disallow null symlinks got somehow taken
as an argument to disallow all "invalid" symlinks then.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]>, Dima Dorfman write
s:
>Jens Schweikhardt <[EMAIL PROTECTED]> writes:
>> hello, world\n
>>
>> with a system cvsupped June 6th I can reliably reproduce a
>> [panic]
>> when I try to unmount a deleted mdconfig device. Here's the recipe:
>>
>> # file iso is a Freebsd
Jens Schweikhardt <[EMAIL PROTECTED]> writes:
> hello, world\n
>
> with a system cvsupped June 6th I can reliably reproduce a
> [panic]
> when I try to unmount a deleted mdconfig device. Here's the recipe:
>
> # file iso is a Freebsd 4.3 Wind River CD image made with
> # dd if=/dev/cd0c of=file.
Please excuse me if you've seen this in questions, but I found a
relevancy to current: If I drop back to 4.3 release, this system boots
every time with no hangs observed in half a dozen tries in either UP
or SMP mode. Anyone else seeing similar?
thanks,
dave c
- Forwarded message from Dave
On Sun, Jun 17, 2001 at 11:48:41AM -0400, Joseph A. Mallett wrote:
> > If we do need some of the functionality of libgmp in the base-system,
> > then we really should import some newer version of libgmp, instead of
> > trying to make our own new library. I dont really like reinventing
> > wheels
On Sun, 17 Jun 2001, Giorgos Keramidas wrote:
>
> If we do need some of the functionality of libgmp in the base-system,
> then we really should import some newer version of libgmp, instead of
> trying to make our own new library. I dont really like reinventing
> wheels :)
>
Unless you are the on
On Sat, Jun 16, 2001 at 11:38:45PM -0700, Peter Wemm wrote:
> It should not be too hard to have build a lightweight 'libbignum' that
> is extracted from the openssl sources and make that available in the base
> system. It would not be hard to convert the lib*mp consumers to use the
> libbignum (
On Sun, Jun 17, 2001 at 23:02:50 +1000, Bruce Evans wrote:
>
> So disallowing null symlinks would actually unbreak /etc/malloc.conf.
>
> Further debugging shows that the main bug is in the kernel.
> stat(2) on a null symlink bogusly succeeds and classifies the symlink
> as a directory. ln(1) ju
On Sat, 16 Jun 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "Steve O'Hara-Smith" writes:
> : I would argue loud and long that changing that *would* be broken. There
> : is never a guarantee (or even an implication) that a symlink points to a
> : valid directory entry (think unmou
hello, world\n
with a system cvsupped June 6th I can reliably reproduce a
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x22
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01b67e2
sta
y]ExTCgzWubNX
http://www.job-rex.com/
ͶßܵÄAWubNXÅ·B
ËRÅ·ª
¡¢Ä¢éïÐÌ]¿É«µÄ¢Ü·©H
WubNXÍ»ÝLAAbv®ÌlA
sÍ é¯ÇdddAÆ¢¤lÌ®ðx·é
LAAbvxTCgÅ·B
¡ÜÅ]E®Å¬Êðã
41 matches
Mail list logo
