Date: Mon, 18 Sep 2000 13:23:36 -0400 (EDT) From: Bosko Milekic <bmilekic@jehovah.technokratis.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/21362: [PATCH] mbuf M_RDONLY flag: to be continued... Message-ID: <200009181723.e8IHNa618503@jehovah.technokratis.com>
next in thread | raw e-mail | index | archive | help
>Number: 21362 >Category: kern >Synopsis: Adds M_RDONLY to external storage mbufs >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Sep 18 10:30:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Bosko Milekic >Release: FreeBSD 5.0-CURRENT i386 >Organization: N/A >Environment: FreeBSD 5.0-CURRENT >Description: Here is a working pre-SMPng patch adding M_RDONLY flag and macro to mbufs that have an ext_buf attached. It is pre-SMPng and should probably just be left sitting here (with this PR) until we're finished threading this area of the code, and then merged, possibly modified, and committed, if deemed necessary. The diff can be found here: http://www.technokratis.com/code/mbuf/mbuf_rdonly.patch Idea for this is in part from dwmalone, in part to Ian Dowse. They should review/add to this before it's committed. Due to the SMPng delay, let it just sit for now. The M_RDONLY flag and the macro, by the way, allow for us to determine uniformally whether the external storage in question is safe to be tampered with/written to, or not. See code and list archives (-net, specifically) for details. >How-To-Repeat: Not applicable. >Fix: Not applicable. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009181723.e8IHNa618503>