- Linux-stable-mirror - lists.linaro.org

[PATCH 5.15 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification

by Ziyang Xuan

5.15 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."), but these are incomplete. There are some patches that have not been backported including key pre-patches commit d38afeec26ed ("tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy()."). Without them, there are some memory leak bugs. Backport complete patchset for inet6_destroy_sock() call modification. Kuniyuki Iwashima (5): udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). include/net/ipv6.h | 2 ++ include/net/udp.h | 2 +- include/net/udplite.h | 8 -------- net/dccp/dccp.h | 1 + net/dccp/ipv6.c | 15 ++++++++------- net/dccp/proto.c | 8 +++++++- net/ipv4/udp.c | 9 ++++++--- net/ipv4/udplite.c | 8 ++++++++ net/ipv6/af_inet6.c | 15 ++++++++++++++- net/ipv6/ipv6_sockglue.c | 20 ++++++++------------ net/ipv6/ping.c | 6 ------ net/ipv6/raw.c | 2 -- net/ipv6/tcp_ipv6.c | 8 +------- net/ipv6/udp.c | 17 ++++++++++++++--- net/ipv6/udp_impl.h | 1 + net/ipv6/udplite.c | 9 ++++++++- net/l2tp/l2tp_ip6.c | 2 -- net/mptcp/protocol.c | 7 ------- net/sctp/socket.c | 29 +++++++++++++++++++++-------- 19 files changed, 100 insertions(+), 69 deletions(-) -- 2.25.1

2 years, 4 months

1
5
0 0

[PATCH 5.10 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification

by Ziyang Xuan

5.10 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."), but these are incomplete. There are some patches that have not been backported including key pre-patches commit d38afeec26ed ("tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy()."). Without them, there are some memory leak bugs. Backport complete patchset for inet6_destroy_sock() call modification. Kuniyuki Iwashima (5): udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). include/net/ipv6.h | 2 ++ include/net/udp.h | 2 +- include/net/udplite.h | 8 -------- net/dccp/dccp.h | 1 + net/dccp/ipv6.c | 15 ++++++++------- net/dccp/proto.c | 8 +++++++- net/ipv4/udp.c | 9 ++++++--- net/ipv4/udplite.c | 8 ++++++++ net/ipv6/af_inet6.c | 15 ++++++++++++++- net/ipv6/ipv6_sockglue.c | 20 ++++++++------------ net/ipv6/ping.c | 6 ------ net/ipv6/raw.c | 2 -- net/ipv6/tcp_ipv6.c | 8 +------- net/ipv6/udp.c | 17 ++++++++++++++--- net/ipv6/udp_impl.h | 1 + net/ipv6/udplite.c | 9 ++++++++- net/l2tp/l2tp_ip6.c | 2 -- net/mptcp/protocol.c | 7 ------- net/sctp/socket.c | 29 +++++++++++++++++++++-------- 19 files changed, 100 insertions(+), 69 deletions(-) -- 2.25.1

2 years, 4 months

1
5
0 0

[PATCH 5.4 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification

by Ziyang Xuan

5.4 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."), but these are incomplete. There are some patches that have not been backported including key pre-patches commit d38afeec26ed ("tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy()."). Without them, there are some memory leak bugs. Backport complete patchset for inet6_destroy_sock() call modification. Kuniyuki Iwashima (5): udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). include/net/ipv6.h | 2 ++ include/net/udp.h | 2 +- include/net/udplite.h | 8 -------- net/dccp/dccp.h | 1 + net/dccp/ipv6.c | 15 ++++++++------- net/dccp/proto.c | 8 +++++++- net/ipv4/udp.c | 9 ++++++--- net/ipv4/udplite.c | 8 ++++++++ net/ipv6/af_inet6.c | 15 ++++++++++++++- net/ipv6/ipv6_sockglue.c | 20 ++++++++------------ net/ipv6/ping.c | 6 ------ net/ipv6/raw.c | 2 -- net/ipv6/tcp_ipv6.c | 8 +------- net/ipv6/udp.c | 17 ++++++++++++++--- net/ipv6/udp_impl.h | 1 + net/ipv6/udplite.c | 9 ++++++++- net/l2tp/l2tp_ip6.c | 2 -- net/sctp/socket.c | 29 +++++++++++++++++++++-------- 18 files changed, 100 insertions(+), 62 deletions(-) -- 2.25.1

2 years, 4 months

1
5
0 0

[PATCH 4.19 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification

by Ziyang Xuan

4.19 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."), but these are incomplete. There are some patches that have not been backported including key pre-patches commit d38afeec26ed ("tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy()."). Without them, there are some memory leak bugs. Backport complete patchset for inet6_destroy_sock() call modification. Kuniyuki Iwashima (5): udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). include/net/ipv6.h | 2 ++ include/net/udp.h | 2 +- include/net/udplite.h | 8 -------- net/dccp/dccp.h | 1 + net/dccp/ipv6.c | 15 ++++++++------- net/dccp/proto.c | 8 +++++++- net/ipv4/udp.c | 9 ++++++--- net/ipv4/udplite.c | 8 ++++++++ net/ipv6/af_inet6.c | 15 ++++++++++++++- net/ipv6/ipv6_sockglue.c | 20 ++++++++------------ net/ipv6/ping.c | 6 ------ net/ipv6/raw.c | 2 -- net/ipv6/tcp_ipv6.c | 8 +------- net/ipv6/udp.c | 17 ++++++++++++++--- net/ipv6/udp_impl.h | 1 + net/ipv6/udplite.c | 9 ++++++++- net/l2tp/l2tp_ip6.c | 2 -- net/sctp/socket.c | 29 +++++++++++++++++++++-------- 18 files changed, 100 insertions(+), 62 deletions(-) -- 2.25.1

2 years, 4 months

1
5
0 0

[PATCH 4.14 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification

by Ziyang Xuan

4.14 LTS has backported commit ca43ccf41224 ("dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.") and commit 62ec33b44e0f ("net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues()."), but these are incomplete. There are some patches that have not been backported including key pre-patches commit d38afeec26ed ("tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct().") and commit b5fc29233d28 ("inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy()."). Without them, there are some memory leak bugs. Backport complete patchset for inet6_destroy_sock() call modification. Kuniyuki Iwashima (5): udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). include/net/ipv6.h | 2 ++ include/net/udp.h | 2 +- include/net/udplite.h | 8 -------- net/dccp/dccp.h | 1 + net/dccp/ipv6.c | 15 ++++++++------- net/dccp/proto.c | 8 +++++++- net/ipv4/udp.c | 9 ++++++--- net/ipv4/udplite.c | 8 ++++++++ net/ipv6/af_inet6.c | 15 ++++++++++++++- net/ipv6/ipv6_sockglue.c | 20 ++++++++------------ net/ipv6/ping.c | 6 ------ net/ipv6/raw.c | 2 -- net/ipv6/tcp_ipv6.c | 8 +------- net/ipv6/udp.c | 17 ++++++++++++++--- net/ipv6/udp_impl.h | 1 + net/ipv6/udplite.c | 9 ++++++++- net/l2tp/l2tp_ip6.c | 2 -- net/sctp/socket.c | 29 +++++++++++++++++++++-------- 18 files changed, 100 insertions(+), 62 deletions(-) -- 2.25.1

2 years, 4 months

1
5
0 0

Hej solsken

by mk

Hej min kära, Jag är ledsen att jag stör dig och inkräktar på din integritet. Jag är singel, ensam och i behov av en omtänksam, kärleksfull och romantisk följeslagare. Jag är en hemlig beundrare och skulle vilja utforska möjligheten att lära mig mer om varandra. Jag vet att det är konstigt att kontakta dig på det här sättet och jag hoppas att du kan förlåta mig. Jag är en blyg person och det är det enda sättet jag vet att jag kan få din uppmärksamhet. Jag vill bara veta vad du tycker och min avsikt är inte att förolämpa dig. Jag hoppas att vi kan vara vänner om det är vad du vill, även om jag vill vara mer än bara en vän. Jag vet att du har några frågor att ställa och jag hoppas att jag kan tillfredsställa en del av din nyfikenhet med några svar. Jag tror på talesättet att för världen är du bara en person, men för någon speciell är du världen, allt jag vill ha är kärlek, romantisk omsorg och uppmärksamhet från en speciell följeslagare som jag hoppas skulle vara du. Jag hoppas att detta meddelande kommer att bli början på en långsiktig kommunikation mellan oss, skicka bara ett svar på detta meddelande, det kommer att göra mig glad. Puss och kram, Marion.

2 years, 4 months

1
0
0 0

Ciao raggio di sole, come stai?

by MK

Mi dispiace disturbarti e invadere la tua privacy. Sono single, solitario e bisognoso di un compagno premuroso, amorevole e romantico. Sono un ammiratore segreto e vorrei esplorare l'opportunità di farlo saperne di più l'uno sull'altro. So che è strano contattarti in questo modo e spero che tu possa perdonarmi. Sono una persona timida e questo è l'unico modo in cui so di poter attirare la tua attenzione. Voglio semplicemente per sapere cosa ne pensate e la mia intenzione non è di offendervi. Spero che possiamo essere amici se è quello che vuoi, anche se lo vorrei essere più di un semplice amico. So che hai alcune domande da fare chiedi e spero di poter soddisfare alcune delle tue curiosità con alcuni risposte. Credo nel detto che "per il mondo sei solo una persona, ma per qualcuno di speciale tu sei il mondo'. Tutto quello che voglio è amore, cure e attenzioni romantiche da una compagna speciale quale sono io sperando saresti tu. Spero che questo messaggio sia l'inizio di un lungo periodo comunicazione tra di noi, è sufficiente inviare una risposta a questo messaggio, it mi renderà felice. Baci e abbracci, Marion.

2 years, 4 months

1
0
0 0

Re: [PATCH pre-6.4] btrfs: dev-replace: error out if we have unrepaired metadata error during

by Torstein Eide

> This is for pre-6.4 kernels, as scrub code goes through a huge rework. > > [BUG] > Even before the scrub rework, if we have some corrupted metadata failed > to be repaired during replace, we still continue replace and let it > finish just as there is nothing wrong: > > BTRFS info (device dm-4): dev_replace from /dev/mapper/test-scratch1 (devid 1) to /dev/mapper/test-scratch2 started > BTRFS warning (device dm-4): tree block 5578752 mirror 1 has bad csum, has 0x00000000 want 0xade80ca1 > BTRFS warning (device dm-4): tree block 5578752 mirror 0 has bad csum, has 0x00000000 want 0xade80ca1 > BTRFS warning (device dm-4): checksum error at logical 5578752 on dev /dev/mapper/test-scratch1, physical 5578752: metadata leaf (level 0) in tree 5 > BTRFS warning (device dm-4): checksum error at logical 5578752 on dev /dev/mapper/test-scratch1, physical 5578752: metadata leaf (level 0) in tree 5 > BTRFS error (device dm-4): bdev /dev/mapper/test-scratch1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 > BTRFS warning (device dm-4): tree block 5578752 mirror 1 has bad bytenr, has 0 want 5578752 > BTRFS error (device dm-4): unable to fixup (regular) error at logical 5578752 on dev /dev/mapper/test-scratch1 > BTRFS info (device dm-4): dev_replace from /dev/mapper/test-scratch1 (devid 1) to /dev/mapper/test-scratch2 finished > > This can lead to unexpected problems for the result fs. > > [CAUSE] > Btrfs reuses scrub code path for dev-replace to iterate all dev extents. > > But unlike scrub, dev-replace doesn't really bother to check the scrub > progress, which records all the errors found during replace. > > And even if we checks the progress, we can not really determine which > errors are minor, which are critical just by the plain numbers. > (remember we don't treat metadata/data checksum error differently). > > This behavior is there from the very beginning. > > [FIX] > Instead of continue the replace, just error out if we hit an unrepaired > metadata sector. > > Now the dev-replace would be rejected with -EIO, to inform the user. > Although it also means, the fs has some metadata error which can not be > repaired, the user would be super upset anyway. If one sector is bad in metadata how much secondary data is damaged? As someone who recently had to remove, and currently replace a disk. it is upsetting, if it stopped if we stopped because 0,01% of data is unrepairable, if we can save the other 99,99%. Can we have it continue, print an error message to standard out, and a way for the user to delete or copy it (with som option like -force-delete or --force-copy) with the error to the new disk? "Metadata at block 5578752 is damaged and unrepaired. Skipping. Read `man btrfs-replace` for more info. " At the end if possible, list files affected by the damaged metadata blocks. In man answer: How can the user know what files are connected to the metadata? How can a user decide what to do with the damaged metadata? At minimum, can there be some useful info to the info to the error output? like "Replace has stopped, due to reading unrepaired metadata block, was working on block 5578752, se `dmesg` for more details. (\s Sorry but you are currently f..k)" > > The new dmesg would look like this: > > BTRFS info (device dm-4): dev_replace from /dev/mapper/test-scratch1 (devid 1) to /dev/mapper/test-scratch2 started > BTRFS warning (device dm-4): tree block 5578752 mirror 1 has bad csum, has 0x00000000 want 0xade80ca1 > BTRFS warning (device dm-4): tree block 5578752 mirror 1 has bad csum, has 0x00000000 want 0xade80ca1 > BTRFS error (device dm-4): unable to fixup (regular) error at logical 5570560 on dev /dev/mapper/test-scratch1 physical 5570560 > BTRFS warning (device dm-4): header error at logical 5570560 on dev /dev/mapper/test-scratch1, physical 5570560: metadata leaf (level 0) in tree 5 > BTRFS warning (device dm-4): header error at logical 5570560 on dev /dev/mapper/test-scratch1, physical 5570560: metadata leaf (level 0) in tree 5 > BTRFS error (device dm-4): stripe 5570560 has unrepaired metadata sector at 5578752 > BTRFS error (device dm-4): btrfs_scrub_dev(/dev/mapper/test-scratch1, 1, /dev/mapper/test-scratch2) failed -5 > > CC: stable(a)vger.kernel.org > Signed-off-by: Qu Wenruo <wqu(a)suse.com> > --- > I'm not sure how should we merge this patch. > > The misc-next is already merging the new scrub code, but the problem is > there for all old kernels thus we need such fixes. > > Maybe we can merge this fix before the scrub rework, then the rework, > and finally the better fix using reworked interface? > --- > fs/btrfs/scrub.c | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c > index ef4046a2572c..71f64b9bcd9f 100644 > --- a/fs/btrfs/scrub.c > +++ b/fs/btrfs/scrub.c > @@ -195,6 +195,7 @@ struct scrub_ctx { > struct mutex wr_lock; > struct btrfs_device *wr_tgtdev; > bool flush_all_writes; > + bool has_meta_failed; > > /* > * statistics > @@ -1380,6 +1381,8 @@ static int scrub_handle_errored_block(struct scrub_block *sblock_to_check) > btrfs_err_rl_in_rcu(fs_info, > "unable to fixup (regular) error at logical %llu on dev %s", > logical, btrfs_dev_name(dev)); > + if (is_metadata) > + sctx->has_meta_failed = true; > } > > out: > @@ -3838,6 +3841,12 @@ static noinline_for_stack int scrub_stripe(struct scrub_ctx *sctx, > > blk_finish_plug(&plug); > > + /* > + * If we have metadata unable to be repaired, we should error > + * out the dev-replace. > + */ > + if (sctx->is_dev_replace && sctx->has_meta_failed && ret >= 0) > + ret = -EIO; > if (sctx->is_dev_replace && ret >= 0) { > int ret2; > -- Torstein Eide Torsteine(a)gmail.com

2 years, 4 months

2
1
0 0

Hello sunshine, how are you?

by MK

I sent an email to you yesterday but since I did not get a response, I thought probably you did not receive it so I decided to send it again and hopefully I will get a response this time around. I am a secret admirer and would like to explore the opportunity to learn more about each other. I know it is strange to contact you this way and I hope you can forgive me. I am a shy person and this is the only way I know I could get your attention. I just want to know what you think and my intention is not to offend you. I hope we can be friends if that is what you want, although I wish to be more than just a friend. I know you have a few questions to ask and I hope I can satisfy some of your curiosity with a few answers. I believe in the saying that 'to the world you are just one person, but to someone special you are the world'. All I want is love, romantic care and attention from a special companion which I am hoping would be you. I hope this message will be the beginning of a long term communication between us, simply send a reply to this message, it will make me happy. Hugs and kisses, Marion.

2 years, 4 months

1
0
0 0

+ relayfs-fix-out-of-bounds-access-in-relay_file_read.patch added to mm-hotfixes-unstable branch

by Andrew Morton

The patch titled Subject: relayfs: fix out-of-bounds access in relay_file_read has been added to the -mm mm-hotfixes-unstable branch. Its filename is relayfs-fix-out-of-bounds-access-in-relay_file_read.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patche… This patch will later appear in the mm-hotfixes-unstable branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via the mm-everything branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there every 2-3 working days ------------------------------------------------------ From: Zhang Zhengming <zhang.zhengming(a)h3c.com> Subject: relayfs: fix out-of-bounds access in relay_file_read Date: Wed, 19 Apr 2023 12:02:03 +0800 There is a crash in relay_file_read, as the var from point to the end of last subbuf. The oops looks something like: pc : __arch_copy_to_user+0x180/0x310 lr : relay_file_read+0x20c/0x2c8 Call trace: __arch_copy_to_user+0x180/0x310 full_proxy_read+0x68/0x98 vfs_read+0xb0/0x1d0 ksys_read+0x6c/0xf0 __arm64_sys_read+0x20/0x28 el0_svc_common.constprop.3+0x84/0x108 do_el0_svc+0x74/0x90 el0_svc+0x1c/0x28 el0_sync_handler+0x88/0xb0 el0_sync+0x148/0x180 We get the condition by analyzing the vmcore: 1). The last produced byte and last consumed byte both at the end of the last subbuf 2). A softirq calls function(e.g __blk_add_trace) to write relay buffer occurs when an program is calling relay_file_read_avail(). relay_file_read relay_file_read_avail relay_file_read_consume(buf, 0, 0); //interrupted by softirq who will write subbuf .... return 1; //read_start point to the end of the last subbuf read_start = relay_file_read_start_pos //avail is equal to subsize avail = relay_file_read_subbuf_avail //from points to an invalid memory address from = buf->start + read_start //system is crashed copy_to_user(buffer, from, avail) Link: https://lkml.kernel.org/r/20230419040203.37676-1-zhang.zhengming@h3c.com Fixes: 341a7213e5c1 ("kernel/relay.c: fix read_pos error when multiple readers") Signed-off-by: Zhang Zhengming <zhang.zhengming(a)h3c.com> Reviewed-by: Zhao Lei <zhao_lei1(a)hoperun.com> Reviewed-by: Zhou Kete <zhou.kete(a)h3c.com> Cc: Pengcheng Yang <yangpc(a)wangsu.com> Cc: Jens Axboe <axboe(a)kernel.dk> Cc: <stable(a)vger.kernel.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> --- kernel/relay.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/kernel/relay.c~relayfs-fix-out-of-bounds-access-in-relay_file_read +++ a/kernel/relay.c @@ -989,7 +989,8 @@ static size_t relay_file_read_start_pos( size_t subbuf_size = buf->chan->subbuf_size; size_t n_subbufs = buf->chan->n_subbufs; size_t consumed = buf->subbufs_consumed % n_subbufs; - size_t read_pos = consumed * subbuf_size + buf->bytes_consumed; + size_t read_pos = (consumed * subbuf_size + buf->bytes_consumed) + % (n_subbufs * subbuf_size); read_subbuf = read_pos / subbuf_size; padding = buf->padding[read_subbuf]; _ Patches currently in -mm which might be from zhang.zhengming(a)h3c.com are relayfs-fix-out-of-bounds-access-in-relay_file_read.patch

2 years, 4 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror