linux-kernel - Re: [PATCH] macb: RLE and BNA handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090330140456.07eb48b8@hskinnemoen-d830>
Date:	Mon, 30 Mar 2009 14:04:56 +0200
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	Erik Waling <erik.waling@...ftel.se>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] macb: RLE and BNA handling

Erik Waling wrote:
> Have you had the time to check the patch below? These two issues still
> needs to be addressed.

Yeah...sorry for not responding earlier.

> If you are unsure of the BNA part you could at least pass the RLE part
> upstreams since it happens more frequently.

Right. I have to admit I'm not at all convinced about the BNA part...it
seems to me like the only scenario when it makes a difference is when
the ring is so small that it can't hold an entire frame. And if that's
the case, isn't the easiest solution to just increase the size of the
ring?

So, could you please split the patch up into the following parts:
  1. TX RLE handling
  2. Call macb_rx() regardless of the status
  3. Handle incomplete RX frames
  4. Special case for RX BNA

Then I can pass on the first three, and we can keep discussing the last
one, which is the one I'm not sure about.

Haavard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/