similar to: [Bridge] [GIT PULL] sysctl changes for v6.6-rc1

Displaying 20 results from an estimated 1700 matches similar to: "[Bridge] [GIT PULL] sysctl changes for v6.6-rc1"

2023 Jul 31
2
[Bridge] [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
> Joel Granados (14): > sysctl: Prefer ctl_table_header in proc_sysctl > sysctl: Use ctl_table_header in list_for_each_table_entry > sysctl: Add ctl_table_size to ctl_table_header > sysctl: Add size argument to init_header > sysctl: Add a size arg to __register_sysctl_table > sysctl: Add size to register_sysctl > sysctl: Add size arg to __register_sysctl_init
2023 Sep 06
0
[Bridge] [GIT PULL] sysctl changes for v6.6-rc1
On Wed, Sep 06, 2023 at 01:58:49PM +0200, Alexey Gladkov wrote: > On Tue, Aug 29, 2023 at 01:44:55PM -0700, Luis Chamberlain wrote: > > The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5: > > > > Linux 6.5-rc1 (2023-07-09 13:53:13 -0700) > > > > are available in the Git repository at: > > > >
2023 Aug 07
3
[Bridge] [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
On Mon, Jul 31, 2023 at 02:36:50PM -0700, Luis Chamberlain wrote: > > Joel Granados (14): > > sysctl: Prefer ctl_table_header in proc_sysctl > > sysctl: Use ctl_table_header in list_for_each_table_entry > > sysctl: Add ctl_table_size to ctl_table_header > > sysctl: Add size argument to init_header > > sysctl: Add a size arg to __register_sysctl_table
2023 Aug 08
0
[Bridge] [PATCH v2 11/14] networking: Update to register_net_sysctl_sz
On Tue, Aug 08, 2023 at 01:20:36PM +0200, Przemek Kitszel wrote: > On 7/31/23 09:17, Joel Granados wrote: > > Move from register_net_sysctl to register_net_sysctl_sz for all the > > networking related files. Do this while making sure to mirror the NULL > > assignments with a table_size of zero for the unprivileged users. > > ... > > const char *dev_name_source;
2023 Aug 08
0
[Bridge] [PATCH v2 11/14] networking: Update to register_net_sysctl_sz
On Tue, Aug 08, 2023 at 01:20:36PM +0200, Przemek Kitszel wrote: > On 7/31/23 09:17, Joel Granados wrote: > > Move from register_net_sysctl to register_net_sysctl_sz for all the > > networking related files. Do this while making sure to mirror the NULL > > assignments with a table_size of zero for the unprivileged users. > > > > We need to move to the new function
2019 Nov 04
1
Gluster v6.6 missing in repos (CentOS 7)
Hi All, Am I the only one that doesn't see the GlusterFS v6.6 ? It was released last week and I thought that it will be here in a day or 2 . Best Regards, Strahil Nikolov
2023 May 15
5
[Bridge] [PATCH net-next 1/2] bridge: Add a limit on FDB entries
A malicious actor behind one bridge port may spam the kernel with packets with a random source MAC address, each of which will create an FDB entry, each of which is a dynamic allocation in the kernel. There are roughly 2^48 different MAC addresses, further limited by the rhashtable they are stored in to 2^31. Each entry is of the type struct net_bridge_fdb_entry, which is currently 128 bytes big.
2006 Feb 06
3
TDM04B FXO Asterisk@Home
I would like to install a TDM04B with Asterisk@Home 2.4 and Asterisk@Home 1.5 but I didn't find documentation about this installation. Thanks in advance, Nelson -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060206/85ff5252/attachment.htm
2011 Jan 09
2
[LLVMdev] Increasing TargetRegisterInfo::FirstVirtualRegister?
On Jan 7, 2011, at 11:25 AM, Dale Johannesen wrote: > We might want to make physical registers negative and virtuals positive, or vice versa. Then FirstVirtualRegister is 0 or 1, and we could get rid of those annoying subtractions of FirstVirtualRegister all over the virtual-register-handling passes. Since 0 is used all over the place as "invalid register" it is probably best to
2017 Oct 31
2
[RFC] ASan: patches to support 32-byte shadow granularity
I've prepared a preliminary set of patches that makes ASan work with 32-byte shadow granularity, and I would like to get some feedback on those patches as well as my general plan. Some background: I am porting ASan to the Myriad platform. I'm looking to break up that port into components that may be useful/relevant to other platforms -- the first of those pieces is the ability to use a
2008 Jun 17
1
GXW 4108 asterisk configuration
Dear, I'm having problems with the configuration of this gateway(GrandStream GXW 4108), I used the instructions from GrandStream but it doesn't work. Someone has a good configuration for this gateway? Thanks in advance, Nelson -------------- next part -------------- An HTML attachment was scrubbed... URL:
2005 Aug 30
1
call attend to spanish
Hello group, I'm running asterisk @ home 1.5 - I would like to change these messages(call attend) to Spanish, how I can do that. Thanks, Nelson
2023 Aug 08
2
[Bridge] [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
On Mon, Aug 07, 2023 at 07:50:44PM -0700, Chris Maness wrote: > I tried running the current mainline kernel (current Arch Linux) with > simple single MUX socket (ax0) using LinFBB. I was a happy camper as > it seemed to work fine at first, then the system just slowed to a > crawl. I am wondering if any of these patches are addressing this > behavior. If its a regressio no. >
2017 Oct 31
1
[RFC] ASan: patches to support 32-byte shadow granularity
+ more asan folks, please CC them to the code reviews. Also please make sure llvm-commits is CC-ed (cfe-commits for clang changes) On Tue, Oct 31, 2017 at 2:29 PM, Walter Lee <waltl at google.com> wrote: > I've prepared a preliminary set of patches that makes ASan work with > 32-byte shadow granularity, and I would like to get some feedback on > those patches as well as my
2023 Aug 07
3
[Bridge] [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
On Mon, Aug 07, 2023 at 04:00:49PM -0700, Chris Maness wrote: > When are these likely to hit the mainline release code? linux-next tomorrow. The first 7 patches are scheduled for mainline as they were merged + tested without any hiccups. These last few patches I'll wait and see. If nothing blows up on linux-next perhaps I'll include them to Linux for mainline during the next merge
2012 Feb 29
1
[LLVMdev] Proposed implementation of N3333 hashing interfaces for LLVM (and possible libc++)
On 29 February 2012 09:35, Chandler Carruth <chandlerc at google.com> wrote: > I still think we can do more, but it's already much faster than the existing LLVM one except for the issue Tobias pointed out w/ modulo-4 key sizes. I'm going to investigate this OK, but this is a VERY big exception! Almost any non-string data anyone wants to hash will be a multiple of 4 bytes in
2011 Jan 07
0
[LLVMdev] Increasing TargetRegisterInfo::FirstVirtualRegister?
We might want to make physical registers negative and virtuals positive, or vice versa. Then FirstVirtualRegister is 0 or 1, and we could get rid of those annoying subtractions of FirstVirtualRegister all over the virtual-register-handling passes. Since 0 is used all over the place as "invalid register" it is probably best to leave this alone, let FirstVirtualRegister be 1, and simply
2015 Oct 08
5
ilist/iplist are broken (maybe I'll fix them?)
I've been digging into some undefined behaviour stemming from how ilist is typically configured. r247937, r247944, and r247978 caused a UBSan failure to start firing on our Green Dragon bots, and after an IRC conversation between David and Nick and Mehdi, we added a blacklist: -- $echo "src:$WORKSPACE/llvm/include/llvm/CodeGen/MachineFunction.h" >> sanitize.blacklist --
2011 Jan 07
3
[LLVMdev] Increasing TargetRegisterInfo::FirstVirtualRegister?
On 01/07/2011 02:07 AM, Chris Lattner wrote: > > Unless your goal is to merge this work onto LLVM mainline, the best thing to do is a local hack in your tree. > > -Chris Yes, I will create a patch for my tree to increase FirstVirtualRegister. Would this be a good change to include in 2.9?
2015 Nov 23
2
bind-to-interface option
On 11/23/15 4:50 PM, Damien Miller wrote: > On Sun, 22 Nov 2015, David Ahern wrote: > >> Hi: >> >> The openssh suite of commands have an option to specify address (e.g, >> ListenAddress for sshd) but I do not see support for bind-to-interface. >> >> The motivating use case for me is using openssh commands (sshd, ssh, scp, >> sftp) with the recent VRF