On Mon, Dec 16, 2013 at 09:58:58PM +0100, Gianluca Anzolin wrote:
> On Mon, Dec 16, 2013 at 09:27:20PM +0100, Gianluca Anzolin wrote:
> > On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
> > > On Mon, Dec 16, 2013 at 02:34:12PM -0500,
On Mon, Dec 16, 2013 at 09:27:20PM +0100, Gianluca Anzolin wrote:
> On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
> > On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
> > >
> > > This solution is acceptable to me, but I think
On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
> On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
> >
> > This solution is acceptable to me, but I think the comment should briefly
> > explain why this fix is necessary, and the changel
On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
>
> This solution is acceptable to me, but I think the comment should briefly
> explain why this fix is necessary, and the changelog should explain why in
> detail.
>
> Perhaps with a fixme comment that rfcomm_tty_install() should
On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
This solution is acceptable to me, but I think the comment should briefly
explain why this fix is necessary, and the changelog should explain why in
detail.
Perhaps with a fixme comment that rfcomm_tty_install() should just
On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
This solution is acceptable to me, but I think the comment should briefly
explain why this fix is necessary, and the changelog should explain why in
detail
On Mon, Dec 16, 2013 at 09:27:20PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
This solution is acceptable to me, but I think the comment should briefly
explain why
On Mon, Dec 16, 2013 at 09:58:58PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 09:27:20PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 09:20:44PM +0100, Gianluca Anzolin wrote:
On Mon, Dec 16, 2013 at 02:34:12PM -0500, Peter Hurley wrote:
This solution
On Sun, Dec 15, 2013 at 09:03:35AM -0500, Peter Hurley wrote:
> On 12/15/2013 06:24 AM, Gianluca Anzolin wrote:
> >On Fri, Dec 13, 2013 at 12:35:26AM +0100, Alexander Holler wrote:
> >>Am 12.12.2013 21:36, schrieb Peter Hurley:
> >>
> >>>>What curre
On Fri, Dec 13, 2013 at 12:35:26AM +0100, Alexander Holler wrote:
> Am 12.12.2013 21:36, schrieb Peter Hurley:
>
> >> What currently happens is that when one kills rfcomm (and any other
> >> terminal which might use that tty), the entry in /dev doesn't
> >> disappear. That means the same call to
On Fri, Dec 13, 2013 at 12:35:26AM +0100, Alexander Holler wrote:
Am 12.12.2013 21:36, schrieb Peter Hurley:
What currently happens is that when one kills rfcomm (and any other
terminal which might use that tty), the entry in /dev doesn't
disappear. That means the same call to refcomm
On Sun, Dec 15, 2013 at 09:03:35AM -0500, Peter Hurley wrote:
On 12/15/2013 06:24 AM, Gianluca Anzolin wrote:
On Fri, Dec 13, 2013 at 12:35:26AM +0100, Alexander Holler wrote:
Am 12.12.2013 21:36, schrieb Peter Hurley:
What currently happens is that when one kills rfcomm (and any other
On Thu, Jul 25, 2013 at 10:14:36AM +0200, Gianluca Anzolin wrote:
> On Thu, Jul 25, 2013 at 08:26:45AM +0200, Jiri Slaby wrote:
> > On 07/25/2013 07:26 AM, Gianluca Anzolin wrote:
> > > The function tty_port_tty_hangup() could leak a reference to the
> > > tty_struct:
On Thu, Jul 25, 2013 at 08:26:45AM +0200, Jiri Slaby wrote:
> On 07/25/2013 07:26 AM, Gianluca Anzolin wrote:
> > The function tty_port_tty_hangup() could leak a reference to the tty_struct:
> >
> > struct tty_struct *tty = tty_port_tty_get(port);
>
On Thu, Jul 25, 2013 at 08:26:45AM +0200, Jiri Slaby wrote:
On 07/25/2013 07:26 AM, Gianluca Anzolin wrote:
The function tty_port_tty_hangup() could leak a reference to the tty_struct:
struct tty_struct *tty = tty_port_tty_get(port);
if (tty (!check_clocal
On Thu, Jul 25, 2013 at 10:14:36AM +0200, Gianluca Anzolin wrote:
On Thu, Jul 25, 2013 at 08:26:45AM +0200, Jiri Slaby wrote:
On 07/25/2013 07:26 AM, Gianluca Anzolin wrote:
The function tty_port_tty_hangup() could leak a reference to the
tty_struct:
struct tty_struct *tty
!= NULL and the second condition is false we never call tty_kref_put and
the reference is leaked.
Fix by always calling tty_kref_put() which accepts a NULL argument.
The patch fixes a regression introduced by commit aa27a094.
Acked-by: Gustavo Padovan
Signed-off-by: Gianluca Anzolin
---
drivers/tty/tty_po
condition is false we never call tty_kref_put and
the reference is leaked.
Fix by always calling tty_kref_put() which accepts a NULL argument.
The patch fixes a regression introduced by commit aa27a094.
Acked-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
Signed-off-by: Gianluca Anzolin
, 2013 at 10:35:35AM +0200, Gianluca Anzolin wrote:
> Hello,
>
> In linux 3.10 in the file drivers/tty/tty_port.c the function
> tty_port_tty_hangup may leak a tty reference:
>
> struct tty_struct *tty = tty_port_tty_get(port);
>
> if (tty &&
, 2013 at 10:35:35AM +0200, Gianluca Anzolin wrote:
Hello,
In linux 3.10 in the file drivers/tty/tty_port.c the function
tty_port_tty_hangup may leak a tty reference:
struct tty_struct *tty = tty_port_tty_get(port);
if (tty (!check_clocal || !C_CLOCAL(tty
_put(tty);
}
If tty != NULL and the second condition is false we never call tty_kref_put and
the reference is leaked.
Fix by nesting two if statements.
Signed-off-by: Gianluca Anzolin
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index 121aeb9..2198f7d 100644
--- a/dri
);
}
If tty != NULL and the second condition is false we never call tty_kref_put and
the reference is leaked.
Fix by nesting two if statements.
Signed-off-by: Gianluca Anzolin gianl...@sottospazio.it
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index 121aeb9..2198f7d 100644
nel bug to me, but it didn't hurt, my PC is working
without problems
Gianluca Anzolin
-
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
bug to me, but it didn't hurt, my PC is working
without problems
Gianluca Anzolin
-
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
Hello,
I've been experiencing since 2.4.2-ac5 (I'm not sure about this) some
oops on one of my PCs: it's a Pentium Classic 166, 84 MB of RAM, kernel
2.4.2-ac12.
It works as a gateway (doing NAT) between my LAN and internet. I use a
ISDN card (Hisax HFC-PCI) and a NE2000 compatible nic (ne.c). I
Hello,
I've been experiencing since 2.4.2-ac5 (I'm not sure about this) some
oops on one of my PCs: it's a Pentium Classic 166, 84 MB of RAM, kernel
2.4.2-ac12.
It works as a gateway (doing NAT) between my LAN and internet. I use a
ISDN card (Hisax HFC-PCI) and a NE2000 compatible nic (ne.c). I
Hello,
I'm experiencing a problem with an old NE2000 card. I use the ne.c
driver provided with 2.4.x kernels. (I'm using 2.4.2-ac11)
The problem is that I can ping the card (with any packet size)
but if I try ssh it doesn't work, the same for other programs which use
TCP. So
Hello,
I'm experiencing a problem with an old NE2000 card. I use the ne.c
driver provided with 2.4.x kernels. (I'm using 2.4.2-ac11)
The problem is that I can ping the card (with any packet size)
but if I try ssh it doesn't work, the same for other programs which use
TCP. So
|No, the problem is the utterly braindamaged way the motherboard chose to
|enable/disable it (*especially* if it's PCI... sheech, port 92h isn't
|exactly something new in that timeframe.)
|
|What PC/motherboard is this, anyway?
It's an olivetti, but maybe they bought the mainboard elsewhere I
|No, the problem is the utterly braindamaged way the motherboard chose to
|enable/disable it (*especially* if it's PCI... sheech, port 92h isn't
|exactly something new in that timeframe.)
|
|What PC/motherboard is this, anyway?
It's an olivetti, but maybe they bought the mainboard elsewhere I
Il giorno Mon, Nov 27, 2000 at 11:08:10AM -0800, H. Peter Anvin scrisse:
|Yes, it can. Unfortunately, some "legacy-free" PCs apparently are
|starting to take the tack that the KBC is legacy. Therefore, the use
|of port 92h is mandatory on those systems.
|
|Port 92h dates back to at the very
Problem solved
I had to bypass the following instructions in arch/i386/boot/setup.S
#
# You must preserve the other bits here. Otherwise embarrasing
# things
# like laptops powering off on boot happen. Corrected version by
# Kira
# Brown from Linux 2.2
#
Problem solved
I had to bypass the following instructions in arch/i386/boot/setup.S
#
# You must preserve the other bits here. Otherwise embarrasing
# things
# like laptops powering off on boot happen. Corrected version by
# Kira
# Brown from Linux 2.2
#
Il giorno Mon, Nov 27, 2000 at 11:08:10AM -0800, H. Peter Anvin scrisse:
|Yes, it can. Unfortunately, some "legacy-free" PCs apparently are
|starting to take the tack that the KBC is legacy. Therefore, the use
|of port 92h is mandatory on those systems.
|
|Port 92h dates back to at the very
Hello
sorry if I'm mailing this twice, but there is a kernel bug in
linux 2.2 and linux 2.4. Linux 2.0 is not affected. I tested also
FreeBSD, OpenBSD, Windows 95 and DOS and they all work.
The problem is that linux doesn't find the video card: after
lilo has loaded the kernel
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke any other program which relies on
/proc/cpuinfo...
I hope the problem will be solved (in the kernel or in every other program which uses
it seems there has been a change in the format of the /proc/cpuinfo file: infact
'flags: ' became 'features: '
This change broke xmms and could broke any other program which relies on
/proc/cpuinfo...
I hope the problem will be solved (in the kernel or in every other program which uses
37 matches
Mail list logo
