linux-kernel - Re: [PATCH 1/2] Refine mutex and rcu method in module.c, kernel<3.2.9>

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: <4F5ACD8A.4000706@gmail.com>
Date:	Sat, 10 Mar 2012 11:42:02 +0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	"Chen, Dennis (SRDC SW)" <Dennis1.Chen@....com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] Refine mutex and rcu method in module.c, kernel<3.2.9>

On 03/07/2012 11:52 PM, Chen, Dennis (SRDC SW) wrote:
>
> diff -u module.ori.c module.c>  module.patch
>
> give more details please?

Let me copy-and-paste it for you as you still don't read it. :)

Documentation/SubmittingPatches

Use "diff -up" or "diff -uprN" to create patches.

All changes to the Linux kernel occur in the form of patches, as
generated by diff(1).  When creating your patch, make sure to create it
in "unified diff" format, as supplied by the '-u' argument to diff(1).
Also, please use the '-p' argument which shows which C function each
change is in - that makes the resultant diff a lot easier to read.
Patches should be based in the root kernel source directory,
not in any lower subdirectory.

To create a patch for a single file, it is often sufficient to do:

         SRCTREE= linux-2.6
         MYFILE=  drivers/net/mydriver.c

         cd $SRCTREE
         cp $MYFILE $MYFILE.orig
         vi $MYFILE      # make your change
         cd ..
         diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch

To create a patch for multiple files, you should unpack a "vanilla",
or unmodified kernel source tree, and generate a diff against your
own source tree.  For example:

         MYSRC= /devel/linux-2.6

         tar xvfz linux-2.6.12.tar.gz
         mv linux-2.6.12 linux-2.6.12-vanilla
         diff -uprN -X linux-2.6.12-vanilla/Documentation/dontdiff \
                 linux-2.6.12-vanilla $MYSRC > /tmp/patch

--
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/