Konstantin Belousov wrote:
> On Wed, Mar 20, 2013 at 11:37:56AM -0400, Rick Macklem wrote:
> > Konstantin Belousov wrote:
> > > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek
> > > wrote:
> > > >
> > > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
> > > > wrote:
> > > > >
Konstantin Belousov wrote:
> On Wed, Mar 20, 2013 at 11:37:56AM -0400, Rick Macklem wrote:
> > Konstantin Belousov wrote:
> > > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek
> > > wrote:
> > > >
> > > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
> > > > wrote:
> > > > >
On Wed, Mar 20, 2013 at 08:58:08PM +0200, Konstantin Belousov wrote:
> On Wed, Mar 20, 2013 at 09:43:20AM -0400, John Baldwin wrote:
> > On Wednesday, March 20, 2013 9:22:22 am Konstantin Belousov wrote:
> > > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek wrote:
> > > >
> > > >
2013/3/19 Jeremy Chadwick :
> On Tue, Mar 19, 2013 at 06:34:24PM +0100, David Demelier wrote:
>> Hello,
>>
>> There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can
>> just say there is a problem in the 9.1-RELEASE because I had no panic
>> before. What afraid me is that my productio
On Wed, Mar 20, 2013 at 09:43:20AM -0400, John Baldwin wrote:
> On Wednesday, March 20, 2013 9:22:22 am Konstantin Belousov wrote:
> > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek wrote:
> > >
> > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
> wrote:
> > > >
> > > >
On Wednesday, March 20, 2013 9:22:22 am Konstantin Belousov wrote:
> On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek wrote:
> >
> > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
wrote:
> > >
> > > I do not like it. As I said in the previous response to Andrey,
> > > I thin
On Wed, Mar 20, 2013 at 11:37:56AM -0400, Rick Macklem wrote:
> Konstantin Belousov wrote:
> > On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek
> > wrote:
> > >
> > > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
> > > wrote:
> > > >
> > > > I do not like it. As I said in the
On Wed, Mar 20, 2013 at 04:20:02PM +0100, Matthias Gamsjager wrote:
> > Due to the security incident, there are still no official FreeBSD
> > packages.
>
> Do you know what the status is on that issue?
I'd also like to find out what the status of this is.
The packages at:
ftp://ftp.freebsd.org
Konstantin Belousov wrote:
> On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek
> wrote:
> >
> > On Mar 20, 2013, at 10:49 AM, Konstantin Belousov
> > wrote:
> > >
> > > I do not like it. As I said in the previous response to Andrey,
> > > I think that moving the vnode_pager_setsize
> Due to the security incident, there are still no official FreeBSD
> packages.
>
Do you know what the status is on that issue?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send an
On Wed, Mar 20, 2013 at 12:13:05PM +0100, Michael Landin Hostbaek wrote:
>
> On Mar 20, 2013, at 10:49 AM, Konstantin Belousov wrote:
> >
> > I do not like it. As I said in the previous response to Andrey,
> > I think that moving the vnode_pager_setsize() after the unlock is
> > better, since it
Comments in line .
---
On Mar 19, 2013, at 1:45 PM, Michael Landin Hostbaek wrote:
>
> On Mar 19, 2013, at 6:35 PM, Jeremy Chadwick wrote:
>
>> On Tue, Mar 19, 2013 at 06:18:06PM +0100, Michael Landin Hostbaek wrote:
>> The kernel panic is happening in NFS-related code. Rick Macklem (and/o
On 20/03/2013, at 22:06, Baptiste Daroussin wrote:
> Empty cwd is normal, it is equivalent to @cwd %%PREFIX%%
OK thanks.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose f
On Wed, Mar 20, 2013 at 09:13:08PM +1030, Daniel O'Connor wrote:
> I noticed I have a lot of ports which have an empty @cwd line in the
> +CONTENTS file (even after reinstalling).
>
> For example a2ps..
> @comment PKG_FORMAT_REVISION:1.1
> @name a2ps-a4-4.13b_4
> @comment ORIGIN:print/a2ps-a4
> @
On Mar 20, 2013, at 10:49 AM, Konstantin Belousov wrote:
>
> I do not like it. As I said in the previous response to Andrey,
> I think that moving the vnode_pager_setsize() after the unlock is
> better, since it reduces races with other thread seeing half-done
> attribute update or making attrib
I noticed I have a lot of ports which have an empty @cwd line in the +CONTENTS
file (even after reinstalling).
For example a2ps..
@comment PKG_FORMAT_REVISION:1.1
@name a2ps-a4-4.13b_4
@comment ORIGIN:print/a2ps-a4
@cwd /usr/local
@pkgdep xineramaproto-1.2.1
@comment DEPORIGIN:x11/xineramaproto
On Tue, Mar 19, 2013 at 07:37:43PM -0400, Rick Macklem wrote:
> Andriy Gapon wrote:
> > on 19/03/2013 19:35 Jeremy Chadwick said the following:
> > > On Tue, Mar 19, 2013 at 06:18:06PM +0100, Michael Landin Hostbaek
> > > wrote:
> > [snip]
> > >> Unread portion of the kernel message buffer:
> > >>
On Mar 20, 2013, at 12:37 AM, Rick Macklem wrote:
>>
> Yep, I'd agree to that. The same bug is in the old NFS client and
> the new NFS client cribbed the code from there.
>
> I have attached a simple patch that unlocks the mutex for the
> vnode_pager_setsize() call. Maybe you could test it?
>
18 matches
Mail list logo